Website review, no card needed

d20pfsrd.com logo

d20pfsrd.com website review

Visit site (opens in a new tab)Reviewed 11 October 202644 issues · 91 checks

This review found 44 issues worth fixing on d20pfsrd.com, 18 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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
934 ms892 msApr 18Oct 3914 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026897 ms
Apr 25, 2026907 ms
May 2, 2026912 ms
May 9, 2026916 ms
May 16, 2026912 ms
May 23, 2026902 ms
May 30, 2026905 ms
Jun 6, 2026903 ms
Jun 13, 2026901 ms
Jun 20, 2026912 ms
Jun 27, 2026919 ms
Jul 4, 2026922 ms
Jul 11, 2026926 ms
Jul 18, 2026918 ms
Jul 25, 2026917 ms
Aug 1, 2026921 ms
Aug 8, 2026929 ms
Aug 15, 2026927 ms
Aug 22, 2026926 ms
Aug 29, 2026924 ms
Sep 5, 2026919 ms
Sep 12, 2026917 ms
Sep 19, 2026921 ms
Sep 26, 2026921 ms
Oct 3, 2026914 ms
Real-visitor tap response (INP)75th percentile, phones
84 ms66 msApr 18Oct 381 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202668 ms
Apr 25, 202672 ms
May 2, 202678 ms
May 9, 202680 ms
May 16, 202682 ms
May 23, 202681 ms
May 30, 202682 ms
Jun 6, 202681 ms
Jun 13, 202681 ms
Jun 20, 202682 ms
Jun 27, 202681 ms
Jul 4, 202680 ms
Jul 11, 202679 ms
Jul 18, 202677 ms
Jul 25, 202675 ms
Aug 1, 202677 ms
Aug 8, 202677 ms
Aug 15, 202678 ms
Aug 22, 202678 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202680 ms
Sep 19, 202680 ms
Sep 26, 202681 ms
Oct 3, 202681 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 d20pfsrd.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

13 to fix26
  • Reduce unused JavaScript

    4.1 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.

  • Render-blocking requests

    3.0 s

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.

  • Use efficient cache lifetimes

    1.8 s · 1.1 MB

    161 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Improve image delivery

    1.4 s · 330 KiB

    2 images could be 330 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Main-thread work: 10.2 s

    A phone's processor spends 10.2 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 26

    26/100

    Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (nitropay.com, confiant-integrations.net and scalibur.io and others), adding 2.8 MB and 3.0 s of main-thread time.

  • nitropay.com adds 518 ms

    518 ms

    nitropay.com costs a phone 518 ms of main-thread work and 302 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.

  • confiant-integrations.net adds 494 ms

    494 ms

    confiant-integrations.net costs a phone 494 ms of main-thread work and 378 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.

  • scalibur.io adds 475 ms

    475 ms

    scalibur.io costs a phone 475 ms of main-thread work and 293 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.

  • Google/Doubleclick Ads adds 398 ms

    398 ms

    Google/Doubleclick Ads costs a phone 398 ms of main-thread work and 688 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.

  • Rubicon Project adds 440 ms

    440 ms

    Rubicon Project costs a phone 440 ms of main-thread work and 139 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.

  • 20 long tasks on the main thread

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

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • Legacy JavaScript

    33 KiB

    Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need.

  • 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.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.0 s

    14.0 s

    Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “If you haven’t got one already, you can create your user ac…”.

  • Time to Interactive: 49.9 s

    49.9 s

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

  • Total Blocking Time: 2.2 s

    2.2 s

    Scripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Speed Index: 9.4 s

    9.4 s

    Visually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.

  • Cumulative Layout Shift: 0.113

    0.113

    The layout shifts by 0.113 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

6 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: 1.2 s

    1.2 s

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

  • Real-user INP: 101 ms

    101 ms

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

  • Real-user CLS: 0.07

    0.07

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 412 ms

    412 ms

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

Images and page weight

1 to fix70
  • Page weight: 5.2 MB in 1,083 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 1,083 requests on a phone: scripts 3.4 MB (97), images 652 KiB (303) and other files 589 KiB (558). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.47 g

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

3 checks passed
  • 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

9 to fixGoogle 8589
  • 73 tap targets too small

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

  • 55 text elements with low contrast

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

  • Links look like plain text

    3 links inside paragraphs rely on colour alone to stand out.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 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 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

5 to fixGoogle 7774
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (8 characters)

    Your title is only 8 characters: “d20PFSRD”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 493 internal links, 68 external

    The homepage links to 493 pages on d20pfsrd.com and 68 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Home”.

  • Canonical URL set

    The canonical URL is https://www.d20pfsrd.com/.

  • 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://www.d20pfsrd.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.d20pfsrd.com/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 (1,085 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.d20pfsrd.com/skills, https://www.d20pfsrd.com/basics-ability-scores, https://www.d20pfsrd.com/traits, https://www.d20pfsrd.com/alignment-description, https://www.d20pfsrd.com/equipment and https://www.d20pfsrd.com/magic-items and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 180 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

5 to fixGoogle 3169
  • 9 broken images

    9 images failed to load on a phone, for example https://ids4.ad.gt/api/v1/ip_match?id=AU1D-0100-001791760904-PTM8A1C5-YBGS.

  • 202 small tap targets

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

  • 42 third-party cookies

    42 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) NotSupportedError: Failed to execute 'browsingTopics' on 'Document': document.browsingTopics() is…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,276 words of copy

    The homepage carries about 1,276 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign up here to subscribe”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Sign up here to subscribe”, “Shop in the Store!” and “Join Our Discord!”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 2 mores (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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 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.

  • 56 other companies contacted

    Loading the homepage contacts 56 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 d20pfsrd.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on d20pfsrd.com, including 19 speed issues, 5 SEO issues and 2 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