midwich.com website review

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

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

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

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

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

3 third-party services load with your homepage (Google CDN, freeprivacypolicy.com and Google Fonts), adding 152 KiB and 68 ms of main-thread time.

About 11 KiB of CSS is downloaded but never applied on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “tile 1 bg”. Most of its time is resource load delay (5.8 s).

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 images (125 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.

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

Certain ARIA roles must be contained by particular parents: 8 elements on the page fail this check, rated critical by axe-core.

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

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

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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.

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 66 pages on midwich.com and 220 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.

There is no https://www.midwich.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 2 pages by a URL that isn't their canonical one, for example https://www.midwich.com/sustainabilityUKI, whose canonical is https://www.midwich.com/campaign/sustainabilityuki. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.midwich.com/campaign/connected has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.midwich.com/campaign/ukidirectory 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.

https://www.midwich.com/about-us/our-history, https://www.midwich.com/sustainabilityUKI, https://www.midwich.com/services/credit-services, https://www.midwich.com/services/it-services, https://www.midwich.com/expertise/marketing-hub and https://www.midwich.com/news-and-events/blogs and 3 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 32 found) 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.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,066 words of visible text.

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