ssssprings.com website review

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

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

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

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

8 third-party services load with your homepage (Webflow, Google Tag Manager and Facebook and others), adding 2.9 MB and 1.5 s of main-thread time.

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

Webflow costs a phone 735 ms of main-thread work and 2.0 MB 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.

Google Tag Manager costs a phone 421 ms of main-thread work and 597 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.

52 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “- LEGACY OF EXCELLENCE - - GLOBAL FOOTPRINT - - CUSTOM MANU…”.

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

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

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

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

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

3s-applied-TsL-logo.png weighs 520 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 3s-applied-TsL-logo.png at 1,998 px wide, shown at 160 px. Resized copies would save about 490 KiB.

Your homepage downloads 3.6 MB in 66 requests on a phone: images 1.8 MB (30), scripts 1.2 MB (13) and fonts 565 KiB (14). Under 2 MB keeps phones on slow connections fast.

2 images (602 KiB) 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.

1 image further down the page (81 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 1.03 g of CO₂e: 123.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

There are 3 <h1> headlines (“CONTENTS”, “MENU” and “[email protected]”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

There is no robots.txt at ssssprings.com/robots.txt, the first file search crawlers ask for.

The homepage links to 18 pages on ssssprings.com and 3 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.

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

https://ssssprings.com/news.html and https://ssssprings.com/declaration.html all use the title “News”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ssssprings.com/about.html, https://ssssprings.com/products.html, https://ssssprings.com/engineering.html, https://ssssprings.com/certificates.html, https://ssssprings.com/news.html and https://ssssprings.com/declaration.html and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://ssssprings.com/news.html has 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.

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

4 images failed to load on a phone, for example https://cdn.prod.website-files.com/611204952e0695fff88a7a68/611204962e069584c48a7a81_ill-western-hem.svg.

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

The homepage carries about 293 words of visible text.

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