Website review, no card needed
goldennumber.net website review
Visit site (opens in a new tab)Reviewed 20 November 202626 issues · 77 checks
This review found 26 issues worth fixing on goldennumber.net, 6 of them high impact, across 77 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.3 s |
| Nov 14, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 90 ms |
| Jun 6, 2026 | 92 ms |
| Jun 13, 2026 | 92 ms |
| Jun 20, 2026 | 86 ms |
| Jun 27, 2026 | 90 ms |
| Jul 4, 2026 | 84 ms |
| Jul 11, 2026 | 85 ms |
| Jul 18, 2026 | 84 ms |
| Jul 25, 2026 | 85 ms |
| Aug 1, 2026 | 100 ms |
| Aug 8, 2026 | 109 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 108 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 102 ms |
| Oct 3, 2026 | 100 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 95 ms |
| Oct 31, 2026 | 90 ms |
| Nov 7, 2026 | 82 ms |
| Nov 14, 2026 | 81 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.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
1.6 s · 310 KiBAbout 310 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 172 KiB10 files are served with short cache lifetimes, so returning visitors download them again (172 KiB).
Google Tag Manager adds 162 ms
162 msGoogle Tag Manager costs a phone 162 ms of main-thread work and 308 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.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and adtrafficquality.google and others), adding 726 KiB and 330 ms of main-thread time.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Render-blocking requests
200 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 ms.
Improve image delivery
150 ms · 25 KiB2 images could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 16 KiBAbout 16 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 142 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 621 ms of it running JavaScript. That is comfortably low.
Server response: 142 ms
142 msYour server sent the HTML in 142 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: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Golden Ratio: Phi, 1.618”.
Cumulative Layout Shift: 0.528
0.528The layout shifts by 0.528 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.22
0.22For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 6.7 s
6.7 sThe page becomes fully interactive after 6.7 s. Good is under 3.8 s.
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 90 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 92 ms
92 msScripts block the page for only 92 ms while loading. Good is under 200 ms.
Images and page weight
About 0.3 g of CO₂ per visit
0.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.27 g of CO₂e: 32.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 971 KiB in 31 requests
971 KiBYour homepage downloads 971 KiB in 31 requests on a phone: scripts 619 KiB (8), fonts 141 KiB (5) and HTML 115 KiB (5). That is a lean page.
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
4 text elements with low contrast
4 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 (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
23 links without text
23 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → 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 48 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (176 characters)
Your title is 176 characters, so Google will cut it off around 60: “The Golden Ratio: Phi, 1.618 - Golden Ratio, Phi, 1.618, and Fibonacci in Math, Nature, A…”.
2 H1 headlines
There are 2 <h1> headlines (“The Golden Ratio: Phi, 1.618” and “The Golden Ratio: Phi, 1.618 (See Index)”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, 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.
177 internal links, 43 external
The homepage links to 177 pages on goldennumber.net and 43 external pages.
5 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Golden Ratio, Phi, 1.618, and Fibonacci in Math, Nature, Art, Design, Beauty and the Face. One source with over 100 art…”.
Canonical URL set
The canonical URL is https://www.goldennumber.net/.
Structured data in place
Structured data found: BreadcrumbList, CollectionPage, Organization, Person 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.goldennumber.net/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.goldennumber.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.
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, logo, sameAs (social profiles) and description; url and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (5,818 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://www.goldennumber.net/contributors, https://www.goldennumber.net/category/resources, https://www.goldennumber.net/contact, https://www.goldennumber.net/golden-ratio-products, https://www.goldennumber.net/site-map and https://www.goldennumber.net/category/phi-basics and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.goldennumber.net/category/resources, https://www.goldennumber.net/category/phi-basics, https://www.goldennumber.net/category/design, https://www.goldennumber.net/category/face-beauty, https://www.goldennumber.net/category/life and https://www.goldennumber.net/category/math and 4 others 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 68 found) and read each the way a search engine does.
5 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.
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
12 small tap targets
12 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 5,817 words of copy
The homepage carries about 5,817 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “The Golden Ratio Book on Amazon”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and “over 1,000 reviews”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
9 other companies contacted
Loading the homepage contacts 9 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 goldennumber.net, 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
- Analytics
- Google Analytics
- Hosting
- Newfold Digital
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on goldennumber.net, including 12 speed issues, 3 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.