raniplast.com website review

5 images could be 861 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

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

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

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

1 third-party service load with your homepage (Vimeo), adding 4.7 MB and 72 ms of main-thread time.

Vimeo costs a phone 72 ms of main-thread work and 4.7 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.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Packaging for Life”.

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

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

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

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

4 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 6.1 MB in 39 requests on a phone: other files 4.3 MB (7), images 1.0 MB (9) and scripts 402 KiB (9). Under 2 MB keeps phones on slow connections fast.

Packaging-for-Life-1080x607.png weighs 701 KiB. On a phone connection a single image that size takes seconds.

4 images (885 KiB) 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

The homepage links to 115 pages on raniplast.com and 6 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.raniplast.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://www.raniplast.com/products/film-conversion, https://www.raniplast.com/products/paper and https://www.raniplast.com/products/energy-and-growing-media are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

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

Opening the homepage sets 3 cookies, 2 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.