Website review, no card needed

journalgazette.net logo

journalgazette.net website review

Visit site (opens in a new tab)Reviewed 24 October 202646 issues · 95 checks

This review found 46 issues worth fixing on journalgazette.net, 17 of them high impact, across 95 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.6 s1.3 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
106 ms88 msMay 2Oct 1797 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202697 ms
May 9, 202690 ms
May 16, 202690 ms
May 23, 202695 ms
May 30, 202695 ms
Jun 6, 2026102 ms
Jun 13, 2026103 ms
Jun 20, 202699 ms
Jun 27, 202699 ms
Jul 4, 2026102 ms
Jul 11, 2026102 ms
Jul 18, 2026101 ms
Jul 25, 2026102 ms
Aug 1, 2026100 ms
Aug 8, 202699 ms
Aug 15, 2026101 ms
Aug 22, 2026102 ms
Aug 29, 2026102 ms
Sep 12, 2026103 ms
Sep 19, 2026104 ms
Sep 26, 2026103 ms
Oct 3, 2026102 ms
Oct 10, 2026100 ms
Oct 17, 202697 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 journalgazette.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

13 to fix45
  • Render-blocking requests

    2.1 s

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

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 5.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google CDN and others), adding 4.3 MB and 2.2 s of main-thread time.

  • Use efficient cache lifetimes

    300 ms · 1.5 MB

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

  • Reduce unused JavaScript

    150 ms · 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 150 ms faster on a phone.

  • Minify JavaScript

    150 ms · 798 KiB

    798 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 697 ms

    697 ms

    Google Tag Manager costs a phone 697 ms of main-thread work and 874 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 503 ms

    503 ms

    Google/Doubleclick Ads costs a phone 503 ms of main-thread work and 510 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 CDN adds 417 ms

    417 ms

    Google CDN costs a phone 417 ms of main-thread work and 764 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,309 HTML elements

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

  • tradingview-widget.com adds 156 ms

    156 ms

    tradingview-widget.com costs a phone 156 ms of main-thread work and 394 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.

  • townnews.com adds 123 ms

    123 ms

    townnews.com costs a phone 123 ms of main-thread work and 572 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 249 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    150 ms · 84 KiB

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

  • Legacy JavaScript

    38 KiB

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

  • Improve image delivery

    29 KiB

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

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

1 checks passed
  • Server response: 26 ms

    26 ms

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

Core Web Vitals

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

  • Time to Interactive: 31.1 s

    31.1 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Largest Contentful Paint: 5.1 s

    5.1 s

    Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Local high schoolers to learn about future careers with AI …”.

  • Speed Index: 7.0 s

    7.0 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user CLS: 0.15

    0.15

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

5 checks passed
  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 133 ms

    133 ms

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 459 ms

    459 ms

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

  • Cumulative Layout Shift: 0.049

    0.049

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

Images and page weight

2 to fix64
  • Page weight: 5.3 MB in 211 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 211 requests on a phone: scripts 4.0 MB (83), other files 443 KiB (47) and images 415 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6acfb4f08bd63.image.jpg 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).

  • About 1.5 g of CO₂ per visit

    1.51 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

7 to fixGoogle 8890
  • 15 tap targets too small

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

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious 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.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

2 checks passed
  • Every image has alt text

    All 72 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 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 8568
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (18 characters)

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

  • Structured data has 4 problems

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

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 257 internal links, 42 external

    The homepage links to 257 pages on journalgazette.net and 42 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.journalgazette.net/.

  • 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.journalgazette.net/sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 3 AI answer engine crawlers

    3 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, logo, 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.journalgazette.net/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.

1 checks passed
  • Text is in the HTML

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.journalgazette.net/tv_listings is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://www.journalgazette.net/advertise, https://www.journalgazette.net/weather, https://www.journalgazette.net/archives, https://www.journalgazette.net/newsletter, https://www.journalgazette.net/local and https://www.journalgazette.net/local/courts and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.journalgazette.net/tv_listings and https://www.journalgazette.net/archives 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 126 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

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

  • 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 a title

    All 13 pages that loaded have a <title>.

Best practices

5 to fixGoogle 6969
  • 2 broken images

    2 images failed to load on a phone, for example https://tpc.googlesyndication.com/simgad/1712134987038839880?.

  • 18 small tap targets

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

  • Deprecated browser APIs

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “syncJsSdk is not defined”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 2 low-resolution images

    2 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

1 to fix93
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 876 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 6 calls to action

    The homepage has 6 calls to action, for example “Sign Up”, “Contact Us” and “Subscribe”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 34 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 1 more (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.

  • 12 cookies set on arrival

    12

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

  • 39 other companies contacted

    Loading the homepage contacts 39 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 journalgazette.net, 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 Tag Manager

Company

Founded
1863

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on journalgazette.net, including 20 speed issues, 5 SEO issues and 1 conversion gap. 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