scmcube.com website review

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

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

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

24 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 825 KiB and 497 ms of main-thread time.

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

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

17 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 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SCM-Shape”.

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

Visually, the page fills in at 6.7 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.

17 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.9 MB in 83 requests on a phone: images 1.7 MB (41), scripts 799 KiB (17) and fonts 336 KiB (7). Under 2 MB keeps phones on slow connections fast.

18 images (1.6 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.

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

1 image is downloaded at several times the size a phone draws it, for example whatsapp-icon.gif at 256 px wide, shown at 60 px. Resized copies would save about 48 KiB.

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

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

1 link inside paragraphs relies on colour alone to stand out.

1 image has no alt text, which hurts accessibility and image search.

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

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

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

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

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

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 69 pages on scmcube.com and 9 external pages.

There is no https://scmcube.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://scmcube.com/blog.html, https://scmcube.com/portfolio.html, https://scmcube.com/request-demo.html and https://scmcube.com/support.html have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

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

2 images are served at too low a resolution for sharp phone screens.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 330 words of visible text.

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