meandem.com website review

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

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

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

A phone's processor spends 6.6 s on main-thread work while loading, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

7 images could be 4.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Global-e and ContentSquare and others), adding 1.4 MB and 1.8 s of main-thread time.

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

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

Global-e costs a phone 396 ms of main-thread work and 136 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.

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

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

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

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

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.

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

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

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

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

Real visitors wait 292 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.

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

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

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

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

Your homepage downloads 8.3 MB in 203 requests on a phone: images 5.4 MB (47), scripts 2.3 MB (61) and fonts 332 KiB (7). Under 2 MB keeps phones on slow connections fast.

image weighs 5.0 MB. On a phone connection a single image that size takes seconds.

1 image (5.0 MB) is 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.

1 image further down the page (5.0 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Headings skip levels (h2 → h4), 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.

The homepage links to 216 pages on meandem.com and 5 external pages.

There is no https://www.meandem.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.meandem.com/us/stores and https://www.meandem.com/us/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.meandem.com/us/contact has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage has only about 239 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (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 40 cookies (measured from a US location before any click).

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