Website review, no card needed
anthology.org website review
Visit site (opens in a new tab)Reviewed 3 November 202632 issues · 73 checks
This review found 32 issues worth fixing on anthology.org, 7 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.2 s · 421 KiBAbout 421 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Improve image delivery
1.1 s · 200 KiB14 images could be 200 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.1 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
4 third-party services on the page
4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Tag Manager and others), adding 809 KiB and 670 ms of main-thread time.
Google CDN adds 605 ms
605 msGoogle CDN costs a phone 605 ms of main-thread work and 742 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.
Reduce unused CSS
330 ms · 96 KiBAbout 96 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 330 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 191 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Use efficient cache lifetimes
47 KiB2 files are served with short cache lifetimes, so returning visitors download them again (47 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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Anthology Home”.
Time to Interactive: 9.8 s
9.8 sThe page becomes fully interactive after 9.8 s. Good is under 3.8 s.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 262 ms
262 msScripts block taps and scrolling for 262 ms in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.056
0.056The layout barely moves while loading (CLS 0.056, good is under 0.1).
Images and page weight
An image on the first screen is lazy-loaded
AN_Wht_Logo-1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (181 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 0.5 g of CO₂ per visit
0.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.52 g of CO₂e: 62.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.8 MB in 56 requests
1.8 MBYour homepage downloads 1.8 MB in 56 requests on a phone: scripts 788 KiB (17), images 390 KiB (22) and other files 352 KiB (1). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
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.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (15 characters)
Your title is only 15 characters: “Anthology, Inc.”. Between 30 and 65 characters leaves room to say what you do and for whom.
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 (Article, BreadcrumbList, Organization and WebPage) but with 2 problems, for example “Article: missing datePublished”.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
27 internal links, 9 external
The homepage links to 27 pages on anthology.org and 9 external pages.
3 checks passed
Meta description: 93 characters
Your meta description is 93 characters: “Anthology, Inc. is an Arizona based literary non profit based in Mesa and working since 1994.”.
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://anthology.org/index.php/component/osmap/?view=xml&id=1&format=xml.
AI search readiness
Parts of the site are closed to 2 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot) and ChatGPT (ChatGPT-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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 https://www.anthology.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (392 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.anthology.org/index.php/calendar is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share a title
https://www.anthology.org/index.php/attending/eventdetail/52/-/re-write-saturdays-at-bookmaze-mesa, https://www.anthology.org/index.php/attending/eventdetail/38/-/2026-mesa-book-festival, https://www.anthology.org/index.php/attending/eventdetail/39/-/2026-mesa-book-festival and https://www.anthology.org/index.php/attending/eventdetail/53/-/re-write-saturdays-at-bookmaze-mesa all use the title “2026 Mesa Book Festival | December 5–6 | Mesa, AZ”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages share a meta description
https://www.anthology.org/index.php/news-posts, https://www.anthology.org/index.php/calendar, https://www.anthology.org/index.php/in-photos, https://www.anthology.org/index.php/black-and-white-awards and https://www.anthology.org/index.php/artsgiving-day use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://www.anthology.org/index.php/calendar, https://www.anthology.org/index.php/in-photos, https://www.anthology.org/index.php/mesa-book-festival, https://www.anthology.org/index.php/black-and-white-awards, https://www.anthology.org/index.php/mesa-book-crawl and https://www.anthology.org/index.php/artsgiving-day have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.anthology.org/index.php/mesa-book-festival and https://www.anthology.org/index.php/sonoran-writers-conference took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.
4 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
12 small tap targets
12 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
7 low-resolution images
7 images are 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
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 392 words of copy
The homepage carries about 392 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: “Mesa Book Festival” and “Mall Crawl Book Fair”.
7 calls to action
The homepage has 7 calls to action, for example “Mesa Book Festival”, “Mall Crawl Book Fair” and “2026 Mesa Book Festival”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Matomo.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
1 cookie set on arrival
1Opening 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.
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 anthology.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Joomla
- Framework
- jQuery
- Analytics
- Google Analytics | Matomo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on anthology.org, including 11 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.