medrock.com website review

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

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

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

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

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

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

7 third-party services load with your homepage (one.store, Stamped.io and Shopify and others), adding 305 KiB and 86 ms of main-thread time.

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

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

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 11.3 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 11.4 s. Good is under 3.8 s.

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

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

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

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.

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

8 buttons have no accessible name, so screen readers announce just “button”.

ARIA attributes must conform to valid values: 3 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.

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

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

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

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 28 characters: “MedRock Inc. – MedRock, Inc.”. 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.

There are 3 <h1> headlines (“”, “Get people moving... Keep people moving” and “HotRock”). One clear main headline is easier for people and search engines.

The homepage links to 64 pages on medrock.com and 7 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.

https://medrock.com/collections/all, https://medrock.com/pages/contact, https://medrock.com/blogs/blog, https://medrock.com/policies/privacy-policy and https://medrock.com/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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