periogen.com website review

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

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

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

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

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

widgetbe.com costs a phone 61 ms of main-thread work and 301 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.

4 third-party services load with your homepage (widgetbe.com, Cloudflare and GoDaddy and others), adding 328 KiB and 84 ms of main-thread time.

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

Polyfills for old browsers add 60 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.

Your largest element takes 20.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Periogen oral rinse and toothpaste products”.

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

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

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

5 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 6.6 MB in 37 requests on a phone: images 6.1 MB (9), scripts 475 KiB (16) and fonts 44 KiB (2). Under 2 MB keeps phones on slow connections fast.

4 images weigh 5.3 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example periogenkitcat.png at 1,500 px wide, shown at 331 px. Resized copies would save about 2.7 MB.

7 images (6.1 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 17 characters: “Periogen | OraTec”. 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.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://oratec.net/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 136 pages on periogen.com and 1 external page.

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.

There is no https://oratec.net/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://oratec.net/home, https://oratec.net/product/therasol-ready-to-use, https://oratec.net/product/therasol-concentrate, https://oratec.net/product/therasol-ready-to-use-with-xylitol, https://oratec.net/product/therasol-mixing-storage-bottles and https://oratec.net/product/therasol-pump and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://oratec.net/home, https://oratec.net/product/therasol-ready-to-use, https://oratec.net/product/therasol-concentrate, https://oratec.net/product/therasol-ready-to-use-with-xylitol, https://oratec.net/product/pocket-care-irrigator and https://oratec.net/product/viajet-ozone-deep-pocket-irrigation-kit and 4 others took over 3 s to send their HTML from our server.

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

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.

The homepage carries about 559 words of visible text.

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