Website review, no card needed

chophairdressing.com logo

chophairdressing.com website review

Visit site (opens in a new tab)Reviewed 28 October 202635 issues · 75 checks

This review found 35 issues worth fixing on chophairdressing.com, 12 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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 chophairdressing.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. chophairdressing.com at 0.8 s0.8 s
  2. chophairdressing.com at 1.7 s1.7 s
  3. chophairdressing.com at 2.5 s2.5 s
  4. chophairdressing.com at 3.4 s3.4 s
  5. chophairdressing.com at 4.2 s4.2 s
  6. chophairdressing.com at 5.1 s5.1 s
  7. chophairdressing.com at 5.9 s5.9 s
  8. chophairdressing.com at 6.8 s6.8 s

Speed

7 to fix58
  • Render-blocking requests

    4.7 s

    43 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.

  • Reduce unused JavaScript

    2.4 s · 447 KiB

    About 447 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Improve image delivery

    1.5 s · 950 KiB

    15 images could be 950 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

  • Font display

    1.1 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).

  • Reduce unused CSS

    900 ms · 194 KiB

    About 194 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 58

    58/100

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

  • Google CDN adds 82 ms

    82 ms

    Google CDN costs a phone 82 ms of main-thread work and 348 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 545 KiB and 206 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 191 ms

    191 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 11.4 s

    11.4 s

    Visually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 15.4 s

    15.4 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

    The first text or image appears after 3.6 s on a phone. Good is under 1.8 s.

  • 31 images without width and height

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

2 checks passed
  • Cumulative Layout Shift: 0.043

    0.043

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

  • Total Blocking Time: 87 ms

    87 ms

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

Images and page weight

4 to fix58
  • Page weight: 3.2 MB in 113 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 113 requests on a phone: images 1.7 MB (24), scripts 894 KiB (40) and fonts 330 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

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

  • 14 images far larger than shown

    213 KiB

    14 images are downloaded at several times the size a phone draws them, for example image5.jpg at 596 px wide, shown at 180 px. Resized copies would save about 213 KiB.

  • 7 images below the first screen load straight away

    7 images further down the page (331 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.91 g

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

Accessibility

5 to fixGoogle 9694
  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9285
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 33 internal links, 12 external

    The homepage links to 33 pages on chophairdressing.com and 12 external pages.

6 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Chop Hairdressing is a cutting and colour service in Wellington. Great Cut. Great Service. Great People. Book an appoin…”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Chop Hairdressing | Cutting + Colour Services”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • 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://chophairdressing.com/sitemap_index.xml.

AI search readiness

1 to fix83
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://chophairdressing.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

5 to fix50
  • 1 linked page is broken

    Your homepage links to https://chophairdressing.com/shop-all, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://chophairdressing.com/product-category/wash-n-rinse is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://chophairdressing.com/info and https://chophairdressing.com/the-team all use the title “Chop Hairdressing Info | Service - Foil - Colour”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://chophairdressing.com/product/chop-voucher and https://chophairdressing.com/product-category/wash-n-rinse have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://chophairdressing.com/editorial, https://chophairdressing.com/the-team, https://chophairdressing.com/contact, https://chophairdressing.com/product-category/wash-n-rinse, https://chophairdressing.com/privacy-policy and https://chophairdressing.com/terms-conditions have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://chophairdressing.com/editorial, https://chophairdressing.com/product/chop-voucher and https://chophairdressing.com/privacy-policy 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://chophairdressing.com/the-team, https://chophairdressing.com/contact and https://chophairdressing.com/product/chop-voucher took over 3 s to send their HTML from our server.

  • 9 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 4 small tap targets

    4 of 12 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 fix78
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 77 words

    The homepage has only about 77 words of visible text; thin pages give Google and first-time buyers little to go on.

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK NOW”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Contact.”, “Book.” and “book now”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 chophairdressing.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
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on chophairdressing.com, including 12 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