Website review, no card needed

ajc.com logo

ajc.com website review

Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 85 checks

This review found 36 issues worth fixing on ajc.com, 14 of them high impact, across 85 checks. The most urgent: cloudfront.net adds 4.2 s. 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
2.7 s2.3 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Oct 31, 20262.5 s
Nov 7, 20262.4 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
201 ms159 msMay 30Nov 14183 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026164 ms
Jun 6, 2026164 ms
Jun 13, 2026164 ms
Jun 20, 2026164 ms
Jun 27, 2026172 ms
Jul 4, 2026178 ms
Jul 11, 2026183 ms
Jul 18, 2026187 ms
Jul 25, 2026181 ms
Aug 1, 2026178 ms
Aug 8, 2026180 ms
Aug 15, 2026185 ms
Aug 22, 2026188 ms
Aug 29, 2026190 ms
Sep 5, 2026192 ms
Sep 12, 2026189 ms
Sep 19, 2026194 ms
Sep 26, 2026196 ms
Oct 3, 2026196 ms
Oct 10, 2026195 ms
Oct 17, 2026188 ms
Oct 24, 2026186 ms
Oct 31, 2026183 ms
Nov 7, 2026182 ms
Nov 14, 2026183 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 ajc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ajc.com at 1.3 s1.3 s
  2. ajc.com at 2.6 s2.6 s
  3. ajc.com at 3.9 s3.9 s
  4. ajc.com at 5.2 s5.2 s
  5. ajc.com at 6.6 s6.6 s
  6. ajc.com at 7.9 s7.9 s
  7. ajc.com at 9.2 s9.2 s
  8. ajc.com at 10.5 s10.5 s

Speed

14 to fix25
  • cloudfront.net adds 4.2 s

    4.2 s

    cloudfront.net costs a phone 4.2 s of main-thread work and 2.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused JavaScript

    1.4 s · 1.8 MB

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

  • Main-thread work: 23.0 s

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

  • Mobile performance score: 25

    25/100

    Your mobile performance score is 25. 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 (cloudfront.net, Other Google APIs/SDKs and Google Tag Manager and others), adding 6.0 MB and 7.3 s of main-thread time.

  • Use efficient cache lifetimes

    850 ms · 3.8 MB

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

  • Improve image delivery

    200 ms · 1.3 MB

    11 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    850 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

  • Google/Doubleclick Ads adds 530 ms

    530 ms

    Google/Doubleclick Ads costs a phone 530 ms of main-thread work and 1.5 MB 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 Tag Manager adds 605 ms

    605 ms

    Google Tag Manager costs a phone 605 ms of main-thread work and 704 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.

  • Other Google APIs/SDKs adds 615 ms

    615 ms

    Other Google APIs/SDKs costs a phone 615 ms of main-thread work and 447 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.

  • Cloudflare CDN adds 544 ms

    544 ms

    Cloudflare CDN costs a phone 544 ms of main-thread work and 298 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.

  • 2,359 HTML elements

    The page has 2,359 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    50 ms · 100 KiB

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

  • Reduce unused CSS

    22 KiB

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Real-user CLS: 0.33

    0.33

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

  • Largest Contentful Paint: 12.5 s

    12.5 s

    Your largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “HeeHaw, a petting zoo miniature donkey, was shot and killed…”.

  • Speed Index: 31.0 s

    31.0 s

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

  • Time to Interactive: 67.3 s

    67.3 s

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

  • Total Blocking Time: 3.7 s

    3.7 s

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

  • Cumulative Layout Shift: 0.191

    0.191

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

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

    +11%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 164 ms to 183 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 2.5 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 167 ms

    167 ms

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

  • 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: 309 ms

    309 ms

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

Images and page weight

1 to fix70
  • Page weight: 32.9 MB in 1,159 requests

    32.9 MB

    Your homepage downloads 32.9 MB in 1,159 requests on a phone: media 22.5 MB (4), scripts 5.3 MB (189) and images 2.4 MB (392). Under 2 MB keeps phones on slow connections fast.

  • About 9.3 g of CO₂ per visit

    9.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 9.32 g of CO₂e: 1118.1 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

5 to fixGoogle 8993
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 16 text elements with low contrast

    16 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 7790
  • Title is long (89 characters)

    Your title is 89 characters, so Google will cut it off around 60: “Atlanta news, Georgia news, Breaking news from The Atlanta Journal-Constitution - AJC.com”.

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

  • 203 internal links, 25 external

    The homepage links to 203 pages on ajc.com and 25 external pages.

7 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Atlanta news, sports, Atlanta weather, entertainment, business and political news from The Atlanta Journal Constitution…”.

  • One H1 headline

    Your main headline reads: “Latest news”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: NewsMediaOrganization, WebPage and WebSite.

  • 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://feeds.ajc.com/arc/outboundfeeds/sitemap-index/?outputType=xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.ajc.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.

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without an H1

    https://www.ajc.com/politics, https://www.ajc.com/accessatl and https://www.ajc.com/sports/varsity have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 to fixGoogle 5488
  • 69 small tap targets

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

  • 33 third-party cookies

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Browser-reported issues

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

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

2 to fix70
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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,920 words of copy

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Subscribe”, “Contact Us” and “Download iOS App”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Tag Manager, Meta Pixel and TikTok Pixel and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 cookies set on arrival

    10

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

  • 35 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 ajc.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 36 issues on ajc.com, including 22 speed issues, 2 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