percona.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Osano CMP and others), adding 1.3 MB and 948 ms of main-thread time.

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

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

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

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

About 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 80 ms faster on a phone.

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

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

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 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 24.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Open Source Database Software & Experts Your Database. No L…”.

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

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

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

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

Real visitors wait 204 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-24, real Chrome visitors' tap response (inp) went from 166 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Scripts block taps and scrolling for 236 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' largest content (lcp) went from 3.3 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.2 MB in 221 requests on a phone: images 2.3 MB (76), scripts 1.6 MB (45) and fonts 94 KiB (6). Under 2 MB keeps phones on slow connections fast.

3 images (655 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.

3 images are downloaded at several times the size a phone draws them, for example Percona_Texture_232.jpg at 1,344 px wide, shown at 350 px. Resized copies would save about 255 KiB.

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

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

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

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 160 pages on percona.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.

https://www.percona.com/mysql/vision has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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

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