meyerus.com website review

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (8.2 MB).

Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

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

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

1 third-party service load with your homepage (Google Fonts), adding 131 KiB and 1 ms of main-thread time.

10 KiB could be saved by minifying CSS.

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 32.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To nourish human connection by inspiring joy for every chef…”.

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

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

Your homepage downloads 18.1 MB in 60 requests on a phone: images 9.6 MB (29), media 8.2 MB (1) and fonts 147 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image (34 KiB) 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.

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

12 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 28 characters: “Meyer US - Meyer Corporation”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No XML sitemap at https://meyerus.com/sitemap.xml, so Google discovers your pages only by following links.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 66 pages on meyerus.com and 18 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://meyerus.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://meyerus.com/about, https://meyerus.com/programs, https://meyerus.com/sustainability, https://meyerus.com/brands, https://meyerus.com/brands/hestan and https://meyerus.com/brands/ruffoni and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Content security policy”).

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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