saberzone.com website review

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

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

Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

Reduce initial server response time. Google estimates savings of 554 ms on a phone.

The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

About 60 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

Your server takes 654 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

3 third-party services load with your homepage (AMP, Google Fonts and Sirv), adding 158 KiB and 130 ms of main-thread time.

1 long task block the main thread while loading, the longest for 106 ms. During a long task the page ignores taps.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB JavaScript is shipped twice across bundles.

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

The layout shifts by 0.688 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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.

3 images are downloaded at several times the size a phone draws them, for example rb1.png at 1,920 px wide, shown at 390 px. Resized copies would save about 632 KiB.

Your homepage downloads 2.1 MB in 51 requests on a phone: images 1.9 MB (21), scripts 140 KiB (6) and HTML 22 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image (473 KiB) is 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.

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

Images must have alternative text: 9 elements on the page fail this check, rated critical by axe-core.

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

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

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

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 on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

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

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

Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption. (1 element).

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

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

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

No XML sitemap at https://theessexlaserclinic.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 167 pages on saberzone.com and 11 external pages.

Your Organization JSON-LD is missing 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.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TOO_MANY_REDIRECTS”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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 has only about 192 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.