primeseo.by website review

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

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

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

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

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

About 38 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 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 284 KiB and 139 ms of main-thread time.

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

1 long task block the main thread while loading, the longest for 98 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.

4 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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.

Снимок-экрана-2022-06-29-в-20.26.26.png weighs 792 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example linkedin-sales-solutions-hMLDD0Gyd4A-unsplash-scaled.jpg at 2,560 px wide, shown at 360 px. Resized copies would save about 637 KiB.

Your homepage downloads 2.5 MB in 38 requests on a phone: images 1.9 MB (15), scripts 405 KiB (9) and fonts 139 KiB (3). Under 2 MB keeps phones on slow connections fast.

9 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images (1.7 MB) 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 0.72 g of CO₂e: 86.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

All page content should be contained by landmarks: 13 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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

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

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

There are 2 <h1> headlines (“Продвижение англоязычных сайтов” and “Пополярные вопросы”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 44 pages on primeseo.by and 8 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://primeseo.by/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://primeseo.by/about, https://primeseo.by/uslugi/seo-usa, https://primeseo.by/uslugi/seo-europe, https://primeseo.by/uslugi/seo-uk, https://primeseo.by/uslugi/raskrutka-sajtov-na-anglijskom-yazyke and https://primeseo.by/uslugi/burzh-trafik and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://primeseo.by/about, https://primeseo.by/case, https://primeseo.by/blog, https://primeseo.by/contact, https://primeseo.by/portfolio/seo-services-for-art-supplies-shop and https://primeseo.by/portfolio/seo-services-for-an-alcohol-distributor and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://primeseo.by/about, https://primeseo.by/case, https://primeseo.by/blog and https://primeseo.by/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://primeseo.by/about, https://primeseo.by/uslugi/seo-usa, https://primeseo.by/uslugi/seo-europe, https://primeseo.by/uslugi/seo-uk, https://primeseo.by/uslugi/raskrutka-sajtov-na-anglijskom-yazyke and https://primeseo.by/uslugi/burzh-trafik and 7 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example http://localhost/uza/wp-content/themes/seo/img/core-img/curve-3.png.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Mixed content”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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