Website review, no card needed
ametllerorigen.com website review
Visit site (opens in a new tab)Reviewed 26 October 202634 issues · 80 checks
This review found 34 issues worth fixing on ametllerorigen.com, 14 of them high impact, across 80 checks. The most urgent: google Tag Manager adds 2.3 s. 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
67DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
2.2 s
4.4 s
6.7 s
8.9 s
11.1 s
13.3 s
15.5 s
17.8 s
Speed
Google Tag Manager adds 2.3 s
2.3 sGoogle Tag Manager costs a phone 2.3 s of main-thread work and 851 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 21.3 s
A phone's processor spends 21.3 s on main-thread work while loading, 17.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 2.7 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Didomi and Cloudflare and others), adding 1.1 MB and 2.5 s of main-thread time.
Improve image delivery
500 ms · 293 KiB6 images could be 293 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Reduce unused JavaScript
150 ms · 592 KiBAbout 592 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
2,145 HTML elements
The page has 2,145 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 51 KiB4 files are served with short cache lifetimes, so returning visitors download them again (51 KiB).
Legacy JavaScript
150 ms · 31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 65 but mobile only 39. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user INP: 709 ms
709 msReal visitors wait 709 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.36
0.36For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.
Total Blocking Time: 12.0 s
12.0 sScripts block taps and scrolling for 12.0 s in total while the page loads. Good is under 200 ms.
Speed Index: 14.5 s
14.5 sVisually, the page fills in at 14.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 20.8 s
20.8 sThe page becomes fully interactive after 20.8 s. Good is under 3.8 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner image”.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
4 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 427 ms
427 msReal visitors wait 427 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 128 requests
2.8 MBYour homepage downloads 2.8 MB in 128 requests on a phone: scripts 1.6 MB (42), images 896 KiB (39) and fonts 131 KiB (5). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
ECOMM_MBPM_BrousRefrigerats_AO_2026_Mobile_CA.jpg 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).
1 image in older formats
1 image (58 KiB) is 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.
About 0.8 g of CO₂ per visit
0.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 95.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (15 elements)
Alternative text of images should not be repeated as text: 15 elements on the page fail this check, rated minor by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (195 characters)
Your meta description is 195 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
244 internal links, 19 external
The homepage links to 244 pages on ametllerorigen.com and 19 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Ametller Origen | Botiga online de fruita, verdura i alimentació”.
Title: 45 characters
Your title is a healthy 45 characters: “Ametller Origen | La Botiga Online més fresca”.
Canonical URL set
The canonical URL is https://www.ametllerorigen.com/ca/online.
Structured data in place
Structured data found: Organization and WebPage.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.ametllerorigen.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://ametllerorigen.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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (745 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://ametllerorigen.com/ca/colleccions has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 195 found) and read each the way a search engine does.
6 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
114 small tap targets
114 of 139 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “pwa-kit-react-sdk.registerServiceWorker ERROR ServiceWorker registration failed {"error":{"name":"TypeError","message":…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 15 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 684 words of copy
The homepage carries about 684 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 ametllerorigen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- AWS
Company
- Employees
- 1,650
- Founded
- 2001
- Headquarters
- Sant Pere Molanta
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on ametllerorigen.com, including 16 speed issues, 3 SEO issues and 3 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.