Website review, no card needed
good.is website review
Visit site (opens in a new tab)Reviewed 18 October 202636 issues · 84 checks
This review found 36 issues worth fixing on good.is, 13 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.5 s |
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 161 ms |
| May 2, 2026 | 163 ms |
| May 9, 2026 | 169 ms |
| May 16, 2026 | 151 ms |
| May 23, 2026 | 153 ms |
| May 30, 2026 | 140 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 200 ms |
| Jun 27, 2026 | 203 ms |
| Jul 4, 2026 | 202 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 176 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 132 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 152 ms |
| Sep 5, 2026 | 149 ms |
| Sep 12, 2026 | 161 ms |
| Sep 19, 2026 | 161 ms |
| Sep 26, 2026 | 162 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 169 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
Speed
Use efficient cache lifetimes
4.6 s · 782 KiB13 files are served with short cache lifetimes, so returning visitors download them again (782 KiB).
Reduce unused JavaScript
3.3 s · 722 KiBAbout 722 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 74). 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 (adthrive.com, Facebook and Google/Doubleclick Ads and others), adding 1.6 MB and 930 ms of main-thread time.
adthrive.com adds 329 ms
329 msadthrive.com costs a phone 329 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.
Render-blocking requests
350 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Facebook adds 283 ms
283 msFacebook costs a phone 283 ms of main-thread work and 320 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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 263 ms. During a long task the page ignores taps.
Google/Doubleclick Ads adds 122 ms
122 msGoogle/Doubleclick Ads costs a phone 122 ms of main-thread work and 334 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.
Improve image delivery
250 ms · 106 KiB6 images could be 106 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Legacy JavaScript
150 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
80 ms · 50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 80 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 74 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 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.
Largest Contentful Paint: 16.7 s
16.7 sYour largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “car tips, mechanic, check engine light, saving money, quick…”.
Time to Interactive: 16.7 s
16.7 sThe page becomes fully interactive after 16.7 s. Good is under 3.8 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 655 ms
655 msScripts block taps and scrolling for 655 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 916 ms
916 msReal visitors wait 916 ms for your server to start answering (75th percentile). Good is under 800 ms.
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
+2%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 161 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 195 ms
195 msReal visitors wait 195 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.3 MB in 173 requests
2.3 MBYour homepage downloads 2.3 MB in 173 requests on a phone: scripts 1.6 MB (45), fonts 211 KiB (4) and images 196 KiB (23). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (28 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 78.4 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
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
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 20 images in the HTML carry an alt attribute.
47 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: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (14 characters)
Your title is only 14 characters: “GOOD - Good.is”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
89 internal links, 17 external
The homepage links to 89 pages on good.is and 17 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.good.is/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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.good.is/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.good.is/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 (651 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://www.good.is/category/news, https://www.good.is/category/society, https://www.good.is/category/science, https://www.good.is/category/health, https://www.good.is/category/culture and https://www.good.is/good-is/newsletter and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.good.is/good-is/newsletter, whose canonical is https://www.good.is/newsletter. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.good.is/good-is/newsletter and https://www.good.is/privacy-policy 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 56 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.
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
1 broken image
1 image failed to load on a phone, for example https://pixel.rubiconproject.com/token?pid=49096&us_privacy=1YNY.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
27 of 31 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 592 words of copy
The homepage carries about 592 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: “SUBSCRIBE”.
3 calls to action
The homepage has 3 calls to action, for example “Subscribe” and “Contact”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 4 mores (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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 2 of them by other companies (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.
62 other companies contacted
Loading the homepage contacts 62 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 good.is, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
Company
- Founded
- 2006
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on good.is, including 18 speed issues, 4 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.