Website review, no card needed
thatsgreatnews.com website review
Visit site (opens in a new tab)Reviewed 28 October 202650 issues · 93 checks
This review found 50 issues worth fixing on thatsgreatnews.com, 19 of them high impact, across 93 checks. The most urgent: render-blocking requests. 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 95 ms |
| May 16, 2026 | 94 ms |
| May 23, 2026 | 92 ms |
| May 30, 2026 | 93 ms |
| Jun 6, 2026 | 94 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 99 ms |
| Jul 18, 2026 | 97 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 100 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 95 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
How it loaded on a phone
0.7 s
1.3 s
2.0 s
2.6 s
3.3 s
3.9 s
4.6 s
5.2 s
Speed
Render-blocking requests
7.2 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.2 s.
Use efficient cache lifetimes
3.9 s · 1.3 MB35 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Reduce unused JavaScript
2.9 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Mobile performance score: 18
18/100Your mobile performance score is 18 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 3.5 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 (Wistia, Google Tag Manager and netsuite.com and others), adding 2.3 MB and 2.2 s of main-thread time.
Wistia adds 932 ms
932 msWistia costs a phone 932 ms of main-thread work and 768 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
760 ms · 180 KiBAbout 180 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 760 ms faster on a phone.
Google Tag Manager adds 563 ms
563 msGoogle Tag Manager costs a phone 563 ms of main-thread work and 520 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.
netsuite.com adds 507 ms
507 msnetsuite.com costs a phone 507 ms of main-thread work and 670 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.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Improve image delivery
313 KiB9 images could be 313 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 258 ms. During a long task the page ignores taps.
Legacy JavaScript
200 ms · 32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Duplicated JavaScript
67 KiB67 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
60 KiB60 KiB could be saved by minifying JavaScript.
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 CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.56
0.56For real visitors the layout shifts by 0.56 (75th percentile). Good is under 0.1.
First Contentful Paint: 9.3 s
9.3 sThe first text or image appears after 9.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 10.5 s
10.5 sYour largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Check our database of 3 million news articles to see if we'…”.
Time to Interactive: 22.8 s
22.8 sThe page becomes fully interactive after 22.8 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.437
0.437The layout shifts by 0.437 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 732 ms
732 msScripts block taps and scrolling for 732 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
35 images without width and height
35 images 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-10-24, real Chrome visitors' tap response (inp) went from 95 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.3 MB in 138 requests
4.3 MBYour homepage downloads 4.3 MB in 138 requests on a phone: scripts 2.1 MB (45), images 1.3 MB (45) and fonts 354 KiB (10). Under 2 MB keeps phones on slow connections fast.
10 images below the first screen load straight away
10 images further down the page (875 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images in older formats
6 images (689 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.
7 images far larger than shown
325 KiB7 images are downloaded at several times the size a phone draws them, for example 68e277a2c61d36a4a000c18a5030ac31c18e1965.jpg at 640 px wide, shown at 150 px. Resized copies would save about 325 KiB.
About 1.2 g of CO₂ per visit
1.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (3 elements)
Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“The Easiest Way to Display Your Article” and “How our clients made their great news into lastin…”). One clear main headline is easier for people and search engines.
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.
31 internal links, 11 external
The homepage links to 31 pages on thatsgreatnews.com and 11 external pages.
4 checks passed
Title: 44 characters
Your title is a healthy 44 characters: “That's Great News | Custom News and Magazine”.
Canonical URL set
The canonical URL is https://www.thatsgreatnews.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.thatsgreatnews.com/sitemap_www.thatsgreatnews.com_Index.xml.
AI search readiness
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.thatsgreatnews.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 (825 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.thatsgreatnews.com/balance, which answers with an error. Visitors hit a dead end and search engines drop it.
8 pages without a meta description
https://www.thatsgreatnews.com/Free-Preview-1, https://www.thatsgreatnews.com/Order-Now, https://www.thatsgreatnews.com/1-pg-plaque, https://www.thatsgreatnews.com/3-pg-plaque_2, https://www.thatsgreatnews.com/3-pg-plaque and https://www.thatsgreatnews.com/4-pg-plaque_2 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.thatsgreatnews.com/Order-Now and https://www.thatsgreatnews.com/Contact-Us have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.thatsgreatnews.com/3-pg-plaque_2 took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
4 checks passed
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Missing source maps
Large scripts ship without source maps.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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
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.
Thin social proof
Social proof on the homepage: 59 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 811 words of copy
The homepage carries about 811 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: “PLACE AN ORDER” and “REGISTER”.
12 calls to action
The homepage has 12 calls to action, for example “Register”, “Place an order” and “Contact us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Microsoft Clarity (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
18 other companies contacted
Loading the homepage contacts 18 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 thatsgreatnews.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on thatsgreatnews.com, including 25 speed issues, 4 SEO issues and 3 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.