pride.md website review

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

50 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).

6 third-party services load with your homepage (Google Tag Manager, yeastar.com and Google Analytics and others), adding 2.5 MB and 1.6 s of main-thread time.

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

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

About 865 KiB of JavaScript is downloaded but never used on this page.

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

yeastar.com costs a phone 644 ms of main-thread work and 1.6 MB 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.

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

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

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

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

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

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.

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 21.4 s. Good is under 3.8 s.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 104 ms to 98 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 72 requests on a phone: scripts 2.2 MB (16), images 819 KiB (29) and fonts 386 KiB (5). Under 2 MB keeps phones on slow connections fast.

hp-products2_678x452-500x355.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images (395 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.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (17 elements).

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

Your title is 85 characters, so Google will cut it off around 60: “PRIDE.MD - Your partner for delivering technological solutions from leading suppliers”.

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

No XML sitemap at https://www.pride.md/sitemap.xml, so Google discovers your pages only by following links.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 155 pages on pride.md and 5 external pages.

There is no https://www.pride.md/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.pride.md/en-compare-products, https://www.pride.md/en-wishlist, https://www.pride.md/about-us, https://www.pride.md/how-do-you-buy, https://www.pride.md/contact-us and https://www.pride.md/service-center and 2 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 78 found) and read each the way a search engine does.

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

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