Website review, no card needed
somaxagro.com website review
Visit site (opens in a new tab)Reviewed 25 October 202652 issues · 82 checks
This review found 52 issues worth fixing on somaxagro.com, 22 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.7 s |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Use efficient cache lifetimes
19.8 s · 29.7 MB98 files are served with short cache lifetimes, so returning visitors download them again (29.7 MB).
Improve image delivery
14.2 s · 20.7 MB55 images could be 20.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.2 s faster on a phone.
Render-blocking requests
3.1 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Reduce unused JavaScript
1.8 s · 304 KiBAbout 304 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 52). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (jQuery CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 970 KiB and 552 ms of main-thread time.
Reduce unused CSS
300 ms · 48 KiBAbout 48 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 544 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Cloudflare CDN adds 3 ms
3 msCloudflare CDN costs a phone 3 ms of main-thread work and 300 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 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 126 ms
126 msYour server sent the HTML in 126 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 53.3 s
53.3 sYour largest element takes 53.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 55.7 s
55.7 sThe page becomes fully interactive after 55.7 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.35
0.35The layout shifts by 0.35 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
43 images without width and height
43 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 270 ms
270 msScripts block taps and scrolling for 270 ms in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
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.
Images and page weight
Page weight: 30.9 MB in 131 requests
30.9 MBYour homepage downloads 30.9 MB in 131 requests on a phone: images 29.7 MB (78), scripts 630 KiB (13) and fonts 435 KiB (5). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 5.9 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
606 KiB6 images are downloaded at several times the size a phone draws them, for example aa7c84948497726bfe0d0ae4971f6714.png at 1,268 px wide, shown at 390 px. Resized copies would save about 606 KiB.
30 images in older formats
30 images (9.0 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.
20 images below the first screen load straight away
20 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 8.7 g of CO₂ per visit
8.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.75 g of CO₂e: 1049.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
No main landmark
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)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
57 links without text
57 visible links have no text or label, so screen readers cannot say where they go.
7 form fields without a label
7 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (5 characters)
Your title is only 5 characters: “Somax”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://somaxagro.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at somaxagro.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
98 internal links, 17 external
The homepage links to 98 pages on somaxagro.com and 17 external pages.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://somaxagro.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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (536 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages share a title
https://somaxagro.com/paraguay, https://somaxagro.com/paraguay/cultivos/soja, https://somaxagro.com/paraguay/cultivos/ma%C3%ADz, https://somaxagro.com/paraguay/cultivos/trigo, https://somaxagro.com/paraguay/cultivos/arroz and https://somaxagro.com/paraguay/cultivos/algod%C3%B3n and 9 others all use the title “Somax”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://somaxagro.com/brasil, https://somaxagro.com/paraguay/cultivos/soja, https://somaxagro.com/paraguay/cultivos/ma%C3%ADz, https://somaxagro.com/paraguay/cultivos/trigo, https://somaxagro.com/paraguay/cultivos/arroz and https://somaxagro.com/paraguay/cultivos/algod%C3%B3n and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://somaxagro.com/paraguay/cultivos/soja, https://somaxagro.com/paraguay/cultivos/ma%C3%ADz, https://somaxagro.com/paraguay/cultivos/trigo, https://somaxagro.com/paraguay/cultivos/arroz, https://somaxagro.com/paraguay/cultivos/algod%C3%B3n and https://somaxagro.com/paraguay/cultivos/sorgo and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://somaxagro.com/paraguay/soluciones, https://somaxagro.com/paraguay/soluciones/agroquimicos, https://somaxagro.com/paraguay/soluciones/semillas, https://somaxagro.com/paraguay/soluciones/fertilizantes, https://somaxagro.com/paraguay/soluciones/nutricion and https://somaxagro.com/paraguay/soluciones/biologicos and 2 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-images.mailchimp.com/embedcode/classic-061523.css' from origin 'https://somaxa…”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
83 of 84 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 654 words of copy
The homepage carries about 654 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Subscribe”.
2 short forms
2 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Privacy and tracking
3 trackers load before any consent
3Before 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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
No consent tool detected
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.
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at somaxagro.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on somaxagro.com, including 18 speed issues, 8 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.