uniteppk.com website review

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

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

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

About 240 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 60. Pages that score under 90 lose visitors before the first paint.

5 third-party services load with your homepage (Facebook, posthog.com and Google Tag Manager and others), adding 633 KiB and 326 ms of main-thread time.

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

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

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

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

6 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 36.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This involves a lot of bravery from both client and agency.…”.

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

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

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

12 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 28.2 MB in 78 requests on a phone: images 27.3 MB (48), scripts 660 KiB (17) and fonts 188 KiB (5). Under 2 MB keeps phones on slow connections fast.

14 images weigh 26.3 MB together. On a phone connection a single image that size takes seconds.

15 images are downloaded at several times the size a phone draws them, for example Slide-1.png at 2,200 px wide, shown at 302 px. Resized copies would save about 18.4 MB.

19 images (26.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.

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

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

Some list items are not inside a list.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 10 characters: “Home - PPK”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There is no robots.txt at uniteppk.com/robots.txt, the first file search crawlers ask for.

The homepage links to 9 pages on uniteppk.com and 8 external pages.

There is no https://www.uniteppk.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.uniteppk.com/work-and-news, https://www.uniteppk.com/production, https://www.uniteppk.com/culture, https://www.uniteppk.com/contact and https://www.uniteppk.com/careers have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.uniteppk.com/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.13.1/css/all.css?ver=2.1.0' from origin 'https://w…”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 849 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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