phmg.com website review

40 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

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

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

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

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Civic and data-crypt.com and others), adding 747 KiB and 786 ms of main-thread time.

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

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

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

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

26 KiB could be saved by minifying CSS.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

8 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 wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Creative expertise, leading technology and human support, w…”. Most of its time is element render delay (9.3 s).

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

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

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

Scripts block taps and scrolling for 646 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.2 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 13.3 MB in 130 requests on a phone: media 10.0 MB (3), scripts 1.9 MB (20) and images 920 KiB (31). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example planet-mark-6-940x600.jpg at 940 px wide, shown at 93 px. Resized copies would save about 226 KiB.

5 images (423 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 3.77 g of CO₂e: 452.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

The homepage links to 84 pages on phmg.com and 10 external pages.

There is no https://phmg.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://phmg.com/uk, https://phmg.com/aus and https://phmg.com/ca all use the title “PHMG — Revolutionising Customer Connections”. Search engines can't tell which page to show for a search, so each competes with the others.

https://phmg.com/our-work, https://phmg.com/blog and https://phmg.com/get-a-free-demo have no meta description, so Google writes the search snippet from whatever text it finds.

https://phmg.com/uk and https://phmg.com/aus use the same meta description. A description written for each page earns more clicks.

https://phmg.com/our-work, https://phmg.com/careers, https://phmg.com/blog, https://phmg.com/about/why-work-with-phmg and https://phmg.com/services/on-hold-marketing have no <h1> headline, so visitors and search engines get no clear main topic.

https://phmg.com/blog, https://phmg.com/contact, https://phmg.com/uk, https://phmg.com/aus, https://phmg.com/ca and https://phmg.com/the-ultimate-guide-to-audio-branding and 1 other took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 410 (Gone)”.

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 3 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.