corob.com website review

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

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

About 1.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 7.3 s faster on a phone.

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

The page has 4,187 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 810 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

7 third-party services load with your homepage (Cookiebot, Google CDN and Google Tag Manager and others), adding 908 KiB and 796 ms of main-thread time.

Cookiebot costs a phone 313 ms of main-thread work and 154 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.

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

Google Tag Manager costs a phone 218 ms of main-thread work and 307 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 2.3 s on main-thread work while loading, 762 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

18 KiB could be saved by minifying CSS.

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

10 KiB could be saved by minifying JavaScript.

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.

Real visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 5.3 s (75th percentile). Good is under 1.8 s.

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

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

Your largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “COROB is a global technology leader in developing and manuf…”. Most of its time is element render delay (7.3 s).

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

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

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

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

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

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

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

Your homepage downloads 20.8 MB in 189 requests on a phone: images 16.3 MB (61), scripts 2.7 MB (107) and stylesheets 1.6 MB (7). Under 2 MB keeps phones on slow connections fast.

34 images are downloaded at several times the size a phone draws them, for example IN-CAN-production-line.png at 1,200 px wide, shown at 158 px. Resized copies would save about 13.8 MB.

13 images weigh 8.0 MB together. On a phone connection a single image that size takes seconds.

40 images (15.4 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.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Your meta description is 187 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.

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

The homepage links to 277 pages on corob.com and 4 external pages.

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

/products/software/internet-of-corob has no meta description, so Google writes the search snippet from whatever text it finds.

/company/values-behaviors, /company/code-of-conduct, /applications, /applications/paints-coatings, /applications/inks and /applications/specialty-chemicals and 7 others took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://analytics.google.com/g/collect?v=2&tid=G-X8PZQWTS8V&gtm=45je6aq1v9135617104za20gxf1&_p=179314941…”.

Chrome logged issues while loading the page (“Content security policy”).

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

X-XSS-Protection is set to “1; mode=block, 1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

corob.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

corob.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

Your longest form asks for 24 fields (11 required). Every extra field lowers completion.

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

DMARC is set to p=none, so mail pretending to be corob.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 4 cookies (measured from a US location before any click).

Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.