scibpaints.com website review

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

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

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

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

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

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

Adobe Tag Manager costs a phone 445 ms of main-thread work and 287 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.

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

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

Facebook costs a phone 198 ms of main-thread work and 316 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.

2 images could be 202 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

9 KiB could be saved by minifying JavaScript.

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

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.

For real visitors the layout shifts by 0.43 (75th percentile). Good is under 0.1.

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

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

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

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

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

Real visitors wait 845 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 3.1 MB in 171 requests on a phone: scripts 2.1 MB (59), images 622 KiB (44) and fonts 166 KiB (6). Under 2 MB keeps phones on slow connections fast.

homebanner4-m.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 0.88 g of CO₂e: 105.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element hidden from screen readers can still receive keyboard focus.

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

2 images have no alt text, which hurts accessibility and image search.

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

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

14 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor 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 h3 → h5), which makes the page harder to scan with a screen reader.

Your title is 66 characters, so Google will cut it off around 60: “Trusted Wall Painting, Home Painting & Waterproofing - Scib Paints”.

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

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

23 links have no real href, so search engines can't follow them.

Your meta description is 190 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://www.scibpaints.com/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 72 pages on scibpaints.com and 20 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.

https://www.scibpaints.com/content/ap/eg/en/home.logout.html has no <title>, so Google invents the link text in results.

https://www.scibpaints.com/en/home.html and / all use the title “Trusted Wall Painting, Home Painting & Waterproofing - Scib Paints”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.scibpaints.com/content/ap/eg/en/home/store-locator.html, https://www.scibpaints.com/content/ap/eg/en/home/products/paints-and-textures/interior-walls/plain-finishes.html, https://www.scibpaints.com/content/ap/eg/en/home/catalogue/colour-catalogue.html, https://www.scibpaints.com/content/ap/eg/en/home.logout.html, https://www.scibpaints.com/en/home/products/paints-and-textures.html and https://www.scibpaints.com/en/home/catalogue/colour-catalogue.html and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.scibpaints.com/content/ap/eg/en/home/store-locator.html, whose canonical is https://www.scibpaints.com/en/home/store-locator.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.scibpaints.com/content/ap/eg/en/home/store-locator.html, https://www.scibpaints.com/content/ap/eg/en/home/products/paints-and-textures/interior-walls/plain-finishes.html, https://www.scibpaints.com/content/ap/eg/en/home/catalogue/colour-catalogue.html, https://www.scibpaints.com/content/ap/eg/en/home.logout.html, https://www.scibpaints.com/en/home/services.html and https://www.scibpaints.com/en/home/catalogue/colour-catalogue.html and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.scibpaints.com/content/ap/eg/en/home/catalogue/colour-catalogue.html, https://www.scibpaints.com/content/ap/eg/en/home.logout.html, https://www.scibpaints.com/en/home/products/paints-and-textures.html and https://www.scibpaints.com/en/home/services.html took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.scibpaints.com/en/home.html.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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 ()”.

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

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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