phosagro.com website review

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

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

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

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

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

Your mobile performance score is 46 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

3ebra.net costs a phone 102 ms of main-thread work and 713 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, Cloudflare CDN and cbonds.ru and others), adding 769 KiB and 154 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 7.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 50.1 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 20.8 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 50.3 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.

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

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

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

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

Your homepage downloads 14.7 MB in 76 requests on a phone: scripts 5.2 MB (19), media 4.5 MB (4) and images 2.6 MB (22). Under 2 MB keeps phones on slow connections fast.

6 images (865 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 4.17 g of CO₂e: 500.7 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: 1 element on the page fails this check, rated critical by axe-core.

11 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: 2 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

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

Your title is 83 characters, so Google will cut it off around 60: “PhosAgro company is one of the world’s leading phosphate-based fertilizer producers”.

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

Your meta description is 243 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.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.

There is no https://www.phosagro.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.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.phosagro.com/press/company/report-on-the-results-of-voting-at-the-annual-general-meeting-of-shareholders-of-pjsc-phosagro-30-june-2026, whose canonical is https://www.phosagro.com/press/company. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.phosagro.com/production/fertilizer/azotno-fosfornye-udobreniya/npk-s-151515-10, https://www.phosagro.com/production/fertilizer/azotnye-udobreniya/karbamid-n-462, https://www.phosagro.com/production/fertilizer/azotno-fosfornye-udobreniya/diammofoska-npk-s-102626-1, https://www.phosagro.com/production/fertilizer/azotno-fosfornye-udobreniya/npk-s-82030-2 and https://www.phosagro.com/production/fertilizer/azotno-fosfornye-udobreniya/diammoniyfosfat-np-1846 have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.phosagro.com/press/company/report-on-the-results-of-voting-at-the-annual-general-meeting-of-shareholders-of-pjsc-phosagro-30-june-2026 has 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.com/press/company/notice-on-holding-the-annual-general-meeting-of-shareholders-of-pjsc-phosagro-290526, https://www.phosagro.com/production/fertilizer/azotno-fosfornye-udobreniya/npk-s-151515-10, https://www.phosagro.com/production/fertilizer/azotnye-udobreniya/karbamid-n-462, https://www.phosagro.com/production/fertilizer/azotno-fosfornye-udobreniya/diammofoska-npk-s-102626-1 and https://www.phosagro.com/production/fertilizer/azotno-fosfornye-udobreniya/npk-s-82030-2 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.

11 of 35 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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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