msspal.com website review

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

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

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

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

About 165 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.

Your mobile performance score is 54 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

About 55 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.

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

3 third-party services load with your homepage (FontAwesome CDN, userway.org and Google Fonts), adding 153 KiB and 282 ms of main-thread time.

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

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

Desktop scores 89 but mobile only 54. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

3 KiB could be saved by minifying CSS.

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

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

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

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

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

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 6.5 MB in 81 requests on a phone: images 5.9 MB (33), scripts 240 KiB (20) and stylesheets 206 KiB (18). Under 2 MB keeps phones on slow connections fast.

4 images weigh 4.9 MB together. 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 Mss-black.png at 1,677 px wide, shown at 57 px. Resized copies would save about 1.4 MB.

8 images (5.5 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.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

There are 42 <h1> headlines (“0”, “+0” and “+0”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 66 pages on msspal.com and 16 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://msspal.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://msspal.com/features, https://msspal.com/about, https://msspal.com/apic, https://msspal.com/mission-visson, https://msspal.com/management-2 and https://msspal.com/careers and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://msspal.com/features, https://msspal.com/about, https://msspal.com/apic and https://msspal.com/management-2 have no <h1> headline, so visitors and search engines get no clear main topic.

https://msspal.com/pharmaceuticals-2, https://msspal.com/medical-disposable-2 and https://msspal.com/works 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.

https://msspal.com/health-care, https://msspal.com/lab-2, https://msspal.com/medical-disposable-2 and https://msspal.com/fmcg took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 1 trust badge. 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.

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

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.

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

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