Website review, no card needed

archiveofourown.org logo

archiveofourown.org website review

Visit site (opens in a new tab)Reviewed 21 November 202625 issues · 67 checks

This review found 25 issues worth fixing on archiveofourown.org, 6 of them high impact, across 67 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
937 ms859 msMay 30Nov 14928 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026881 ms
Jun 6, 2026882 ms
Jun 13, 2026881 ms
Jun 20, 2026878 ms
Jun 27, 2026877 ms
Jul 4, 2026873 ms
Jul 11, 2026868 ms
Jul 18, 2026871 ms
Jul 25, 2026870 ms
Aug 1, 2026873 ms
Aug 8, 2026875 ms
Aug 15, 2026873 ms
Aug 22, 2026877 ms
Aug 29, 2026879 ms
Sep 5, 2026881 ms
Sep 12, 2026883 ms
Sep 19, 2026882 ms
Sep 26, 2026884 ms
Oct 3, 2026886 ms
Oct 10, 2026884 ms
Oct 17, 2026889 ms
Oct 24, 2026901 ms
Oct 31, 2026905 ms
Nov 7, 2026920 ms
Nov 14, 2026928 ms
Real-visitor tap response (INP)75th percentile, phones
99 ms97 msMay 30Nov 1498 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202697 ms
Jun 6, 202697 ms
Jun 13, 202697 ms
Jun 20, 202698 ms
Jun 27, 202698 ms
Jul 4, 202699 ms
Jul 11, 202699 ms
Jul 18, 202699 ms
Jul 25, 202699 ms
Aug 1, 202699 ms
Aug 8, 202699 ms
Aug 15, 202698 ms
Aug 22, 202698 ms
Aug 29, 202699 ms
Sep 5, 202699 ms
Sep 12, 202699 ms
Sep 19, 202699 ms
Sep 26, 202699 ms
Oct 3, 202699 ms
Oct 10, 202699 ms
Oct 17, 202699 ms
Oct 24, 202698 ms
Oct 31, 202698 ms
Nov 7, 202698 ms
Nov 14, 202698 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 archiveofourown.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. archiveofourown.org at 1.4 s1.4 s
  2. archiveofourown.org at 2.8 s2.8 s
  3. archiveofourown.org at 4.3 s4.3 s
  4. archiveofourown.org at 5.7 s5.7 s
  5. archiveofourown.org at 7.1 s7.1 s
  6. archiveofourown.org at 8.5 s8.5 s
  7. archiveofourown.org at 10.0 s10.0 s
  8. archiveofourown.org at 11.4 s11.4 s

Speed

2 to fix90
  • Render-blocking requests

    1.0 s

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

  • Use efficient cache lifetimes

    300 ms · 131 KiB

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

  • Reduce unused JavaScript

    54 KiB

    About 54 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    22 KiB

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

  • Reduce unused CSS

    17 KiB

    About 17 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

3 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.1 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

2 to fix100
  • Speed Index: 16.3 s

    16.3 s

    Visually, the page fills in at 16.3 s (Speed Index). Good is under 3.4 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

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-11-14, 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).

11 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: 117 ms

    117 ms

    Real visitors wait 117 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: 1.2 s

    1.2 s

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

  • Real-user TTFB: 673 ms

    673 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “AO3 is now up! No data has been deleted. Some features have…”.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.2 s

    1.2 s

    The page is fully interactive after 1.2 s.

Images and page weight

100
  • About 0.06 g of CO₂ per visit

    0.06 g

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

1 checks passed
  • Page weight: 204 KiB in 23 requests

    204 KiB

    Your homepage downloads 204 KiB in 23 requests on a phone: scripts 137 KiB (14), stylesheets 30 KiB (6) and images 28 KiB (2). That is a lean page.

Accessibility

6 to fixGoogle 9888
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    Main 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 main landmark (1 element)

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

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 26 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 9272
  • Title is short (25 characters)

    Your title is only 25 characters: “Home | Archive of Our Own”. 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 canonical URL

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

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

  • No XML sitemap

    No XML sitemap at https://archiveofourown.org/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at archiveofourown.org/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 70 internal links, 9 external

    The homepage links to 70 pages on archiveofourown.org and 9 external pages.

2 checks passed
  • Meta description: 77 characters

    Your meta description is 77 characters: “An Archive of Our Own, a project of the Organization for Transformative Works”.

  • One H1 headline

    Your main headline reads: “Archive of Our Own”.

AI search readiness

1 to fix69
  • 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://archiveofourown.org/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.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    6 pages of 15 loaded without an error (the rest turned automated requests away).

Best practices

1 to fixGoogle 9292
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • 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

6 to fix43
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 27 words

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

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

1 checks passed
  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 archiveofourown.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
jQuery
Hosting
Cloudflare

Company

Founded
2008

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on archiveofourown.org, including 4 speed issues, 7 SEO issues and 6 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