Login

Automated Report

magicui.design

Generated on September 26, 2025 · Domain: magicui.design

Instant Audit

See your site the way search engines feel it

Launch a free crawl in under 30 seconds and get a ranked hit-list of fixes that lift speed, visibility, and trust.

Start Free Analysis
Favicon
magicui.design
2025/09/26
70

Overall Score

77

PageSpeed

63

Website Quality

71

Trust & Security

37

Performance

100

SEO

79

Best Practices

83

Accessibility

Performance
37/100
Largest Contentful Paint
0/25
54.3s
2.5s4.0s
First Contentful Paint
0/10
33.8s
1.8s3.0s
Total Blocking Time
12/30
741ms
200ms400ms
Cumulative Layout Shift
25/25
0.00
0.100.25
Speed Index
0/10
33.8s
3.4s5.4s
SEO
100/100
Page isn’t blocked from indexing
34/34
Document has a `<title>` element
8/8
Document has a meta description
8/8
Page has successful HTTP status code
8/8
Links have descriptive text
8/8
Links are crawlable
8/8
robots.txt is valid
8/8
Image elements have `[alt]` attributes
8/8
Document has a valid `hreflang`
8/8
Best Practices
79/100
Uses HTTPS
18/18
Avoids deprecated APIs
18/18
Uses third-party cookies
0/18
Allows users to paste into input fields
11/11
Avoids requesting the geolocation permission on page load
4/4
Avoids requesting the notification permission on page load
4/4
Displays images with correct aspect ratio
4/4
Serves images with appropriate resolution
4/4
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
4/4
Document uses legible font sizes
4/4
Page has the HTML doctype
4/4
Properly defines charset
4/4
No browser errors logged to the console
4/4
Issues were logged in the `Issues` panel in Chrome Devtools
0/4
Accessibility
83/100
`[aria-*]` attributes match their roles
5/5
`[aria-hidden="true"]` is not present on the document `<body>`
5/5
`[role]`s have all required `[aria-*]` attributes
5/5
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
0/5
`[role]`s are not contained by their required parent element
0/5
`[aria-*]` attributes have valid values
5/5
`[aria-*]` attributes are valid and not misspelled
5/5
Buttons have an accessible name
5/5
Image elements have `[alt]` attributes
5/5
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
5/5
ARIA attributes are used as specified for the element's role
4/4
`[aria-hidden="true"]` elements do not contain focusable descendents
4/4
Elements use only permitted ARIA attributes
4/4
`[role]` values are valid
4/4
Background and foreground colors have a sufficient contrast ratio
4/4
Document has a `<title>` element
4/4
`<frame>` or `<iframe>` elements have a title
4/4
`<html>` element has a `[lang]` attribute
4/4
`<html>` element has a valid value for its `[lang]` attribute
4/4
Links are distinguishable without relying on color.
4/4
Links do not have a discernible name
0/4
No element has a `[tabindex]` value greater than 0
4/4
Touch targets do not have sufficient size or spacing.
0/4
Heading elements appear in a sequentially-descending order
2/2
Uses ARIA roles only on compatible elements
1/1
Deprecated ARIA roles were not used
1/1
Image elements do not have `[alt]` attributes that are redundant text.
1/1

Site Quality

Title
5/20
Magic UI
8 chars (ideal 30–60)
Meta Description
6/15
Beautiful UI components and templates to make your landing page look stunning.
78 chars (ideal 120–160)
Favicon
3/3
Favicon preview
https://magicui.design/favicon.ico
present
Viewport meta
8/8
width=device-width, initial-scale=1
correct (width=device-width, initial-scale=1)
robots.txt
6/6
User-Agent: * Allow: / Disallow: /api/ Disallow: /_next/ Disallow: /public/ Sitemap: https://magicui.design/sitemap.xml
perfect (User-agent + Allow + Sitemap)
Sitemap
7/7
https://magicui.design/sitemap.xml
present
Headings
6/6
H2Command Palette
H1UI library for Design Engineers
H2Showcase
H3Companies choose Magic UI to build their landing pages.
H2What People Are Saying on Twitter
H2Featured on YouTube
correct structure
Schema.org JSON-LD
0/2
missing (consider Organization, Article, Product, or FAQPage schemas)
Canonical URL
0/8
missing (add <link rel='canonical'> to avoid duplicate content)
HTML lang
4/4
en
present
Character encoding
4/4
utf-8
present

Open Graph

Title
3/3
Magic UI
present
Description
3/3
Beautiful UI components and templates to make your landing page look stunning.
present
Image
3/3
Image preview
https://magicui.design/og
present
URL
0/3
missing (add <meta property='og:url'> with full URL)
Type
1/1
website
present

Twitter Cards

Card Type
1/1
summary_large_image
present
Title
1/1
Magic UI
present
Description
1/1
Beautiful UI components and templates to make your landing page look stunning.
present
Image
1/1
Image preview
https://magicui.design/og
present

Security Headers

HTTPS
30/30
HTTPS enabled
HTTP Strict Transport Security
15/15
Strict-Transport-Security: max-age=63072000
Content Security Policy
0/15
missing (should be: Content-Security-Policy: default-src 'self')
Frame Protection
0/5
missing (should be: X-Frame-Options: SAMEORIGIN)
MIME Type Protection
0/5
missing (should be: X-Content-Type-Options: nosniff)

Domain Trust

Domain Rating
25/25
50 (Last sync: 30th July 2025)
1525
Domain Age
1/5
1 years
Registrar
Cloudflare, Inc.
Country
CA

Infrastructure

Provider
Vercel

FAQs

Report-specific answers

Key takeaways for magicui.design pulled from this audit.

How often should I refresh the YourWebsiteScore report for magicui.design?

The latest audit was captured on September 26, 2025.

Re-run the analysis after major deployments or at least once a month so you can spot Core Web Vitals, snippet, or security regressions before they affect rankings or conversions.

Which Lighthouse performance improvements should magicui.design tackle first?

Total Blocking Time (desktop) at 2.8s: reclaim ≈30 points. Split large JavaScript bundles, defer non-critical scripts, and keep heavy work off the main thread to improve responsiveness.

Largest Contentful Paint (mobile) at 54.3s: reclaim ≈25 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.

Total Blocking Time (mobile) at 741ms: reclaim ≈18 points. Split large JavaScript bundles, defer non-critical scripts, and keep heavy work off the main thread to improve responsiveness.

Which Lighthouse SEO audits should magicui.design fix first?

Mobile Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.

Desktop Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.

Which Lighthouse Best Practices should magicui.design fix first?

Uses third-party cookies (mobile) is missing roughly 18 points. Fixing it will raise the Best Practices score and keep magicui.design aligned with modern browser expectations.

Issues were logged in the `Issues` panel in Chrome Devtools (mobile) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep magicui.design aligned with modern browser expectations.

Uses third-party cookies (desktop) is missing roughly 19 points. Fixing it will raise the Best Practices score and keep magicui.design aligned with modern browser expectations.

Issues were logged in the `Issues` panel in Chrome Devtools (desktop) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep magicui.design aligned with modern browser expectations.

Which Lighthouse Accessibility audits should magicui.design fix first?

Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children. (mobile) is missing roughly 5 points. Fixing it will raise the Accessibility score and make magicui.design easier to use.

`[role]`s are not contained by their required parent element (mobile) is missing roughly 5 points. Fixing it will raise the Accessibility score and make magicui.design easier to use.

Links do not have a discernible name (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make magicui.design easier to use.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children. (desktop) is missing roughly 5 points. Fixing it will raise the Accessibility score and make magicui.design easier to use.

`[role]`s are not contained by their required parent element (desktop) is missing roughly 5 points. Fixing it will raise the Accessibility score and make magicui.design easier to use.

Background and foreground colors do not have a sufficient contrast ratio. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make magicui.design easier to use.

Which Website Quality issues should magicui.design fix first?

Title: missing ≈15 points. 8 chars (ideal 30–60). Focus on it to lift magicui.design's Website Quality score.

Meta Description: missing ≈9 points. 78 chars (ideal 120–160). Focus on it to lift magicui.design's Website Quality score.

Canonical URL: missing ≈8 points. Missing (add <link rel='canonical'> to avoid duplicate content). Focus on it to lift magicui.design's Website Quality score.

Which Trust & Security fixes should magicui.design tackle first?

Content Security Policy: missing ≈15 points. Missing (should be: Content-Security-Policy: default-src 'self'). Close this gap to raise magicui.design's Trust & Security score.

Frame Protection: missing ≈5 points. Missing (should be: X-Frame-Options: SAMEORIGIN). Close this gap to raise magicui.design's Trust & Security score.

MIME Type Protection: missing ≈5 points. Missing (should be: X-Content-Type-Options: nosniff). Close this gap to raise magicui.design's Trust & Security score.

Instant Audit

See your site the way search engines feel it

Launch a free crawl in under 30 seconds and get a ranked hit-list of fixes that lift speed, visibility, and trust.

Start Free Analysis