Website review, no card needed

scottmathson.com logo

scottmathson.com website review

Visit site (opens in a new tab)Reviewed 8 November 202627 issues · 70 checks

This review found 27 issues worth fixing on scottmathson.com, 9 of them high impact, across 70 checks. The most urgent: improve image delivery. 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

Full-page screenshot of scottmathson.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix75
  • Improve image delivery

    3.1 s · 1.1 MB

    5 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

  • Mobile performance score: 75

    75/100

    Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    700 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Use efficient cache lifetimes

    500 ms · 150 KiB

    13 files are served with short cache lifetimes, so returning visitors download them again (150 KiB).

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and Cloudflare and others), adding 387 KiB and 198 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused JavaScript

    136 KiB

    About 136 KiB of JavaScript is downloaded but never used on this page.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 124 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    14 KiB

    About 14 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 180 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

3 to fix68
  • Largest Contentful Paint: 7.1 s

    7.1 s

    Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “For more than a decade-plus, I built, marketed, and grew so…”.

  • Time to Interactive: 9.1 s

    9.1 s

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

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 checks passed
  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 41 ms

    41 ms

    Scripts block the page for only 41 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix63
  • 5 images far larger than shown

    943 KiB

    5 images are downloaded at several times the size a phone draws them, for example holland-lake-hike.jpg at 1,920 px wide, shown at 322 px. Resized copies would save about 943 KiB.

  • 6 images in older formats

    6 images (1.2 MB) 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.

  • 4 images below the first screen load straight away

    4 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.47 g

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

1 checks passed
  • Page weight: 1.7 MB in 22 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 22 requests on a phone: images 1.2 MB (8), scripts 327 KiB (5) and fonts 61 KiB (2). That is a lean page.

Accessibility

7 to fixGoogle 7986
  • 40 text elements with low contrast

    40 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Orphan list items

    Some list items are not inside a list.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

    All page content should be contained by landmarks: 22 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10085
  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “Scott Mathson, Maker - Audio Engineer, Musician - Former Web & Marketing Consultant”.

  • Meta description is long (192 characters)

    Your meta description is 192 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.

  • 29 internal links, 47 external

    The homepage links to 29 pages on scottmathson.com and 47 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Welcome to my corner of the web.”.

  • Canonical URL set

    The canonical URL is https://scottmathson.com/.

  • Structured data in place

    Structured data found: 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://scottmathson.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://scottmathson.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 (866 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 10 pages without an H1

    https://scottmathson.com/blog, https://scottmathson.com/about, https://scottmathson.com/blog/2021/11/01/cheapclassictrucks-experiment-domain-name-social-handle-review, https://scottmathson.com/blog/2021/09/15/thank-you-for-the-opportunity-automattic, https://scottmathson.com/blog/2021/04/23/canon-dslr-external-webcam-setup-for-better-laptop-video-quality and https://scottmathson.com/blog/2017/09/19/seo-beginner-guide-optimize-website-for-search and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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

1 to fixGoogle 10093
  • 8 small tap targets

    8 of 15 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

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 5 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 866 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Learn more on my about page.” and “Subscribe”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 4 cookies set on arrival

    4

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 scottmathson.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Jekyll v3.10.0
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on scottmathson.com, including 7 speed issues, 3 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

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