fret-king.com website review

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

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

7 third-party services load with your homepage (YouTube, POWr and Shopify and others), adding 1.1 MB and 407 ms of main-thread time.

YouTube costs a phone 332 ms of main-thread work and 979 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.

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

The page has 1,593 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

8 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Fret-King Collection brings together five or more decad…”.

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

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

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

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.

Your homepage downloads 2.6 MB in 144 requests on a phone: scripts 1.1 MB (37), other files 673 KiB (83) and images 576 KiB (12). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (35 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

7 elements hidden from screen readers can still receive keyboard focus.

1 frame has no title, so screen-reader users cannot tell what it contains.

28 images have no alt text, which hurts accessibility and image search.

6 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 70 characters, so Google will cut it off around 60: “Fret-King guitars, professional working instruments designed in the UK”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 247 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 93 pages on fret-king.com and 12 external pages.

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.

https://fret-king.com/collections/corona-collection, https://fret-king.com/collections/fret-king-corona-classic, https://fret-king.com/collections/corona-custom, https://fret-king.com/collections/country-squire-collection, https://fret-king.com/collections/fret-king-country-squire-classic and https://fret-king.com/collections/fret-king-country-squire-modern-classic and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.

7 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 253 words of visible text.

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.

Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.