synbioconcept.com website review

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

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

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

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

8 third-party services load with your homepage (hcaptcha.com, Shopify and Google CDN and others), adding 7.3 MB and 5.4 s of main-thread time.

About 1.5 MB of JavaScript is downloaded but never used on this page.

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

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

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

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

Google CDN costs a phone 188 ms of main-thread work and 379 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.

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

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

About 24 KiB of CSS is downloaded but never applied on this page.

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.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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

14 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 9.5 MB in 672 requests on a phone: scripts 5.3 MB (411), HTML 1.8 MB (15) and images 1.0 MB (27). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example SC-4-Product-1.png at 2,346 px wide, shown at 360 px. Resized copies would save about 149 KiB.

2 images further down the page (209 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 2.68 g of CO₂e: 322.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 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.

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (2 elements).

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

Your title is 67 characters, so Google will cut it off around 60: “Prebiotic & Probiotic Cleaning Products | Synbio Concept Technology”.

Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.

Your <h1> is empty.

The homepage links to 31 pages on synbioconcept.com and 18 external pages.

https://synbioconcept.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://synbioconcept.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://synbioconcept.com/pages/skincare-personal-care, https://synbioconcept.com/pages/contact, https://synbioconcept.com/collections/all, https://synbioconcept.com/customer_authentication/redirect and https://synbioconcept.com/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://synbioconcept.com/pages/agricultural-services, https://synbioconcept.com/pages/air-purification, https://synbioconcept.com/pages/skincare-personal-care, https://synbioconcept.com/pages/hospitality, https://synbioconcept.com/pages/janitiorial-services and https://synbioconcept.com/pages/water-sanitation and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://synbioconcept.com/collections/all took over 3 s to send its HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

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

1 image is served at too low a resolution for sharp phone screens.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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