phosagro.ru website review

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

About 4.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 20.4 s faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 4.7 s.

About 727 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.8 s faster on a phone.

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

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

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

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

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

3ebra.net costs a phone 70 ms of main-thread work and 712 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.

4 third-party services load with your homepage (3ebra.net, Yandex Metrica and Cloudflare CDN and others), adding 843 KiB and 156 ms of main-thread time.

17 KiB could be saved by minifying JavaScript.

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.

Real visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.

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

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

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

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

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

19 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-31, real Chrome visitors' largest content (lcp) went from 6.1 s to 6.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.8 MB in 135 requests on a phone: scripts 5.2 MB (20), images 2.1 MB (51) and fonts 1.6 MB (17). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 2.79 g of CO₂e: 334.4 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”.

Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

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

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

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

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.

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

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

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

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

Your title is 101 characters, so Google will cut it off around 60: “ФосАгро - один из ведущих мировых производителей фосфорсодержащих удобрений и апатитового…”.

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

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 16 pages on phosagro.ru and 9 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://www.phosagro.ru/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.phosagro.ru/career-education/vacancies, https://www.phosagro.ru/production/fertilizer/azotno-fosfornye-udobreniya/diammofoska-npk-s-102626-1, https://www.phosagro.ru/production/fertilizer/azotno-fosfornye-udobreniya/ammofos-np-1252, https://www.phosagro.ru/production/fertilizer/azotnye-udobreniya/ammiachnaya-selitra-n-344, https://www.phosagro.ru/about and https://www.phosagro.ru/career-education/career and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.phosagro.ru/career-education/vacancies, https://www.phosagro.ru/press/company/fosagro-na-forume-rossiya-afrika-rasskazala-o-planakh-prakticheski-udvoit-postavki-udobreniy-v-afrik, https://www.phosagro.ru/press/company/soobshchenie-o-provedenii-zaochnogo-golosovaniya-dlya-prinyatiya-resheniy-obshchim-sobraniem-aktsion-02122026, https://www.phosagro.ru/press/company/phosagro-board-of-directors-calls-extraordinary-meeting-of-shareholders-for-2-december, https://www.phosagro.ru/production/fertilizer/azotno-fosfornye-udobreniya/diammofoska-npk-s-102626-1 and https://www.phosagro.ru/production/fertilizer/azotno-fosfornye-udobreniya/ammofos-np-1252 and 4 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.phosagro.ru/press/company/soobshchenie-o-provedenii-zaochnogo-golosovaniya-dlya-prinyatiya-resheniy-obshchim-sobraniem-aktsion-02122026, https://www.phosagro.ru/press/company/phosagro-board-of-directors-calls-extraordinary-meeting-of-shareholders-for-2-december, https://www.phosagro.ru/production/fertilizer/azotno-fosfornye-udobreniya/diammofoska-npk-s-102626-1, https://www.phosagro.ru/production/fertilizer/azotno-fosfornye-udobreniya/ammofos-np-1252, https://www.phosagro.ru/production/fertilizer/azotnye-udobreniya/ammiachnaya-selitra-n-344 and https://www.phosagro.ru/about and 2 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

12 of 44 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.”).

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

Large scripts ship without source maps.

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: 2 trust badges. 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 longest form asks for 10 fields (0 required). Every extra field lowers completion.

The homepage has only about 56 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 Yandex Metrica (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.

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