portaltechreply.co.uk website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Maps and others), adding 2.7 MB and 1.1 s of main-thread time.

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

Google Tag Manager costs a phone 500 ms of main-thread work and 562 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.

Google CDN costs a phone 369 ms of main-thread work and 733 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 2.5 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

discoveryreplymedia.com costs a phone 0 ms of main-thread work and 989 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.

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

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

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

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

Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Scripts block taps and scrolling for 329 ms in total while the page loads. Good is under 200 ms.

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.

3 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.6 MB in 77 requests on a phone: scripts 1.7 MB (20), images 1.0 MB (32) and other files 394 KiB (11). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 1f31bf10-0497-4a8b-9907-54ba1fd21f9c.png at 1,080 px wide, shown at 310 px. Resized copies would save about 278 KiB.

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 24 characters: “Portaltech Reply | Reply”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 16 pages on portaltechreply.co.uk and 24 external pages.

There is no https://portaltech.reply.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.

Your homepage links to https://portaltech.reply.com/portaltech/%7BmapsUrl%7D, which answers with an error. Visitors hit a dead end and search engines drop it.

https://portaltech.reply.com/portaltech/en and / all use the title “Portaltech Reply | Reply”. Search engines can't tell which page to show for a search, so each competes with the others.

https://portaltech.reply.com/portaltech/en/clients and https://portaltech.reply.com/portaltech/en/knowledge-hub use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://portaltech.reply.com/portaltech/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://portaltech.reply.com/portaltech/en/knowledge-hub 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.

/ took over 3 s to send its HTML from our server.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

Your longest form asks for 9 fields (6 required). Every extra field lowers completion.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

Opening the homepage sets 4 cookies (measured from a US location before any click).

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