stonylab.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

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

Shopify costs a phone 1.3 s of main-thread work and 2.2 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.

hcaptcha.com costs a phone 1.3 s of main-thread work and 1.2 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.

A phone's processor spends 12.7 s on main-thread work while loading, 6.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

8 third-party services load with your homepage (hcaptcha.com, Shopify and rebuyengine.com and others), adding 4.0 MB and 3.2 s of main-thread time.

61 KiB could be saved by minifying JavaScript.

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

14 images could be 252 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

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

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

rebuyengine.com costs a phone 158 ms of main-thread work and 298 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 KiB could be saved by minifying CSS.

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.

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.

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

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

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

Scripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.

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

Real visitors wait 431 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 177 ms to 291 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.8 MB in 567 requests on a phone: scripts 3.4 MB (244), images 1.3 MB (69) and other files 1.2 MB (195). Under 2 MB keeps phones on slow connections fast.

1500x500.jpg 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).

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

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 8 characters: “StonyLab”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 625 pages on stonylab.com and 27 external pages.

https://stonylab.com/policies/shipping-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://stonylab.com/policies/shipping-policy, https://stonylab.com/pages/follow-us-on-social-media, https://stonylab.com/collections/lab-glassware, https://stonylab.com/collections/adapter, https://stonylab.com/collections/claisen-adapters and https://stonylab.com/collections/connecting-adapter and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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.

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

The homepage carries about 1,362 words of visible text.

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 5 mores (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 37 cookies, 3 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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.