porocel.com website review

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

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

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

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

1 image could be 106 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

5 third-party services load with your homepage (Usercentrics CMP, Facebook and Adobe Tag Manager and others), adding 890 KiB and 418 ms of main-thread time.

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

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

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

9 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 see the first content after 3.4 s (75th percentile). Good is under 1.8 s.

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

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

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

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

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

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

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

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

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

1 image (57 KiB) is 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.

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

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

Your title is only 9 characters: “Catalysts”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

Your hreflang tags are invalid, so Google may show the wrong language version.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 210 pages on porocel.com and 12 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.

Your robots.txt lets ChatGPT search (OAI-SearchBot), Claude search (Claude-SearchBot), Claude (Claude-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://www.evonik.com/en/company/businesslines/ka.html, https://www.evonik.com/de/unternehmen/businesslines/ka.html and https://www.evonik.com/en/markets/market_1345320.html all use the title “Catalysts”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.evonik.com/de/unternehmen/businesslines/ka.html, whose canonical is https://www.evonik.com/en/company/businesslines/ka.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'appendChild')”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 1,286 words of visible text.

Before a visitor clicks anything, the page loads Meta Pixel (measured from a US location before any click). A consent tool (Usercentrics) 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.