Website review, no card needed
standrews.com website review
Visit site (opens in a new tab)Reviewed 18 November 202660 issues · 98 checks
This review found 60 issues worth fixing on standrews.com, 28 of them high impact, across 98 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
49FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.2 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.8 s |
| Nov 7, 2026 | 3.8 s |
| Nov 14, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 258 ms |
| Jun 6, 2026 | 256 ms |
| Jun 13, 2026 | 256 ms |
| Jun 20, 2026 | 256 ms |
| Jun 27, 2026 | 260 ms |
| Jul 4, 2026 | 264 ms |
| Jul 11, 2026 | 267 ms |
| Jul 18, 2026 | 265 ms |
| Jul 25, 2026 | 264 ms |
| Aug 1, 2026 | 262 ms |
| Aug 8, 2026 | 260 ms |
| Aug 15, 2026 | 264 ms |
| Aug 22, 2026 | 264 ms |
| Aug 29, 2026 | 269 ms |
| Sep 5, 2026 | 266 ms |
| Sep 12, 2026 | 262 ms |
| Sep 19, 2026 | 260 ms |
| Sep 26, 2026 | 258 ms |
| Oct 3, 2026 | 262 ms |
| Oct 10, 2026 | 262 ms |
| Oct 17, 2026 | 264 ms |
| Oct 24, 2026 | 267 ms |
| Oct 31, 2026 | 269 ms |
| Nov 7, 2026 | 267 ms |
| Nov 14, 2026 | 267 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
1.5 s
3.1 s
4.6 s
6.2 s
7.7 s
9.2 s
10.8 s
12.3 s
Speed
Reduce unused JavaScript
5.4 s · 7.2 MBAbout 7.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.
YouTube adds 3.4 s
3.4 sYouTube costs a phone 3.4 s of main-thread work and 11.7 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.
Render-blocking requests
1.3 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Main-thread work: 11.3 s
A phone's processor spends 11.3 s on main-thread work while loading, 6.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 9
9/100Your mobile performance score is 9. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
6.1 MB51 images could be 6.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Cloudflare CDN and others), adding 21.9 MB and 3.5 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.
kc-usercontent.com adds 0 ms
0 mskc-usercontent.com costs a phone 0 ms of main-thread work and 9.3 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.
Document request latency
600 msThe HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
578 msReduce initial server response time. Google estimates savings of 578 ms on a phone.
2,925 HTML elements
The page has 2,925 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Other Google APIs/SDKs adds 75 ms
75 msOther Google APIs/SDKs costs a phone 75 ms of main-thread work and 306 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.
Server response: 678 ms
678 msYour server takes 678 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 444 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
223 KiBAbout 223 KiB of CSS is downloaded but never applied on this page.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
8 KiB12 files are served with short cache lifetimes, so returning visitors download them again (8 KiB).
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.
Legacy JavaScript
5 KiBPolyfills for old browsers add 5 KiB JavaScript that modern phones do not need.
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 LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.40
0.40For real visitors the layout shifts by 0.40 (75th percentile). Good is under 0.1.
First Contentful Paint: 14.6 s
14.6 sThe first text or image appears after 14.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 56.0 s
56.0 sYour largest element takes 56.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DISCOVER OUR NEWEST DESTINATION The Craigtoun Course St And…”.
Speed Index: 56.7 s
56.7 sVisually, the page fills in at 56.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 139.5 s
139.5 sThe page becomes fully interactive after 139.5 s. Good is under 3.8 s.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.387
0.387The layout shifts by 0.387 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 355 ms
355 msReal visitors wait 355 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
23 images without width and height
23 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 258 ms to 267 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.3 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 30.4 MB in 315 requests
30.4 MBYour homepage downloads 30.4 MB in 315 requests on a phone: scripts 13.5 MB (79), images 9.6 MB (109) and HTML 3.4 MB (14). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.
33 images below the first screen load straight away
33 images further down the page (5.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
PM-Webpage-Header (1920 x 1080 px) (6).png 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 8.6 g of CO₂ per visit
8.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.62 g of CO₂e: 1034.9 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
9 buttons without a name
9 buttons have no accessible name, so screen readers announce just “button”.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
[role="img"] and [role="image"] elements must have alternative text (1 element)
[role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (37 elements)
All page content should be contained by landmarks: 37 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (4 elements)
Heading levels should only increase by one: 4 elements on the page fail this check, rated moderate by axe-core.
Hidden but focusable
24 elements hidden from screen readers can still receive keyboard focus.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
6 internal links, 0 external
The homepage links to 6 pages on standrews.com and 0 external pages.
2 checks passed
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://standrews.com/static/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
2%A phone browser shows 1,199 words, but the HTML your server sends has only 25. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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://standrews.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.
1 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.
Other pages
4 pages without a title
https://standrews.com/page, https://standrews.com/home-of-golf, https://standrews.com/webcam and https://standrews.com/golf/links-ticketholders have no <title>, so Google invents the link text in results.
4 pages without a meta description
https://standrews.com/page, https://standrews.com/home-of-golf, https://standrews.com/webcam and https://standrews.com/golf/links-ticketholders have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://standrews.com/page, https://standrews.com/home-of-golf, https://standrews.com/webcam and https://standrews.com/golf/links-ticketholders have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://standrews.com/page, https://standrews.com/home-of-golf, https://standrews.com/webcam and https://standrews.com/golf/links-ticketholders have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 pages slow to respond
https://standrews.com/page, https://standrews.com/webcam and https://standrews.com/golf/links-ticketholders took over 3 s to send their HTML from our server.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 4 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
186 distorted images
186 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Title [] is invalid. See https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Tap targets are thumb-sized
55 of 62 tappable elements near the top are at least 24 px.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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,199 words of copy
The homepage carries about 1,199 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “Book a golf lesson”.
1 call to action
The homepage has 1 call to action, for example “Sign up”.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie, 1 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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 standrews.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Azure
Company
- Founded
- 1976
- Headquarters
- Fife
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 60 issues on standrews.com, including 28 speed issues, 7 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.