Website review, no card needed

scryfall.com logo

scryfall.com website review

Visit site (opens in a new tab)Reviewed 11 October 202628 issues · 78 checks

This review found 28 issues worth fixing on scryfall.com, 10 of them high impact, across 78 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.0 s885 msApr 18Oct 3984 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026937 ms
Apr 25, 2026905 ms
May 2, 2026903 ms
May 9, 2026908 ms
May 16, 2026935 ms
May 23, 2026962 ms
May 30, 2026985 ms
Jun 6, 2026994 ms
Jun 13, 2026997 ms
Jun 20, 2026978 ms
Jun 27, 2026958 ms
Jul 4, 2026959 ms
Jul 11, 2026954 ms
Jul 18, 2026981 ms
Jul 25, 2026990 ms
Aug 1, 2026989 ms
Aug 8, 20261.0 s
Aug 15, 2026993 ms
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.0 s
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 20261.0 s
Oct 3, 2026984 ms
Real-visitor tap response (INP)75th percentile, phones
85 ms78 msApr 18Oct 384 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202680 ms
Apr 25, 202679 ms
May 2, 202679 ms
May 9, 202679 ms
May 16, 202679 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202680 ms
Jun 13, 202681 ms
Jun 20, 202682 ms
Jun 27, 202683 ms
Jul 4, 202682 ms
Jul 11, 202681 ms
Jul 18, 202680 ms
Jul 25, 202680 ms
Aug 1, 202681 ms
Aug 8, 202681 ms
Aug 15, 202681 ms
Aug 22, 202681 ms
Aug 29, 202681 ms
Sep 5, 202681 ms
Sep 12, 202682 ms
Sep 19, 202683 ms
Sep 26, 202684 ms
Oct 3, 202684 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of scryfall.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. scryfall.com at 0.4 s0.4 s
  2. scryfall.com at 0.8 s0.8 s
  3. scryfall.com at 1.1 s1.1 s
  4. scryfall.com at 1.5 s1.5 s
  5. scryfall.com at 1.9 s1.9 s
  6. scryfall.com at 2.3 s2.3 s
  7. scryfall.com at 2.6 s2.6 s
  8. scryfall.com at 3.0 s3.0 s

Speed

7 to fix75
  • Render-blocking requests

    1.6 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.

  • Reduce unused JavaScript

    1.1 s · 228 KiB

    About 228 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 75

    75/100

    Your mobile performance score is 75 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    450 ms · 113 KiB

    About 113 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Improve image delivery

    312 KiB

    7 images could be 312 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    300 ms · 11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • scryfall.io adds 0 ms

    0 ms

    scryfall.io costs a phone 0 ms of main-thread work and 453 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google Analytics and Cloudflare and others), adding 774 KiB and 251 ms of main-thread time.

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 98 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    20 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (20 KiB).

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 259 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Scryfall Find cards Advanced Search Syntax Guide All Sets R…”.

  • Time to Interactive: 8.0 s

    8.0 s

    The page becomes fully interactive after 8.0 s. Good is under 3.8 s.

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s on a phone. Good is under 1.8 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 80 ms to 84 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.8 s

    0.8 s

    Real visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 77 ms

    77 ms

    Real visitors wait 77 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 270 ms

    270 ms

    Real visitors wait 270 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 87 ms

    87 ms

    Scripts block the page for only 87 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.38 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.38 g of CO₂e: 45.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed
  • Page weight: 1.3 MB in 22 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 22 requests on a phone: images 690 KiB (10), scripts 470 KiB (5) and stylesheets 117 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 7988
  • 30 tap targets too small

    30 tap targets are too small or too close together to hit reliably with a finger.

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 34 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10087
  • Meta description is short (65 characters)

    Your meta description is only 65 characters: “A fast, powerful, comprehensive Magic: The Gathering card search.”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.

  • 36 internal links, 8 external

    The homepage links to 36 pages on scryfall.com and 8 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Scryfall is a powerful Magic: The Gathering card search”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Scryfall Magic: The Gathering Search”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://scryfall.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (228 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without an H1

    /advanced and /sets have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    /advanced has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 32 small tap targets

    32 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 219 words

    The homepage has only about 219 words of visible text; thin pages give Google and first-time buyers little to go on.

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Register” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 5 other companies contacted

    Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at scryfall.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
Heroku

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on scryfall.com, including 11 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25