Website review, no card needed
auchan.ro website review
Visit site (opens in a new tab)Reviewed 7 November 202642 issues · 88 checks
This review found 42 issues worth fixing on auchan.ro, 18 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.9 s |
| Oct 31, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 280 ms |
| May 23, 2026 | 289 ms |
| May 30, 2026 | 300 ms |
| Jun 6, 2026 | 303 ms |
| Jun 13, 2026 | 303 ms |
| Jun 20, 2026 | 304 ms |
| Jun 27, 2026 | 306 ms |
| Jul 4, 2026 | 310 ms |
| Jul 11, 2026 | 309 ms |
| Jul 18, 2026 | 310 ms |
| Jul 25, 2026 | 309 ms |
| Aug 1, 2026 | 308 ms |
| Aug 8, 2026 | 313 ms |
| Aug 15, 2026 | 318 ms |
| Aug 22, 2026 | 320 ms |
| Aug 29, 2026 | 320 ms |
| Sep 5, 2026 | 319 ms |
| Sep 12, 2026 | 320 ms |
| Sep 19, 2026 | 322 ms |
| Sep 26, 2026 | 326 ms |
| Oct 3, 2026 | 335 ms |
| Oct 10, 2026 | 349 ms |
| Oct 17, 2026 | 363 ms |
| Oct 24, 2026 | 374 ms |
| Oct 31, 2026 | 382 ms |
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
Reduce unused JavaScript
2.6 s · 742 KiBAbout 742 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
vtexassets.com adds 1.6 s
1.6 svtexassets.com costs a phone 1.6 s of main-thread work and 3.2 MB 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.
Mobile performance score: 36
36/100Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Optanon and others), adding 5.2 MB and 2.3 s of main-thread time.
Reduce unused CSS
810 ms · 128 KiBAbout 128 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 810 ms faster on a phone.
Use efficient cache lifetimes
600 ms · 203 KiB38 files are served with short cache lifetimes, so returning visitors download them again (203 KiB).
Google Tag Manager adds 486 ms
486 msGoogle Tag Manager costs a phone 486 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.
Improve image delivery
395 KiB7 images could be 395 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,694 HTML elements
The page has 1,694 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
wawsome.com adds 43 ms
43 mswawsome.com costs a phone 43 ms of main-thread work and 813 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.
Optanon adds 72 ms
72 msOptanon costs a phone 72 ms of main-thread work and 433 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 219 ms. During a long task the page ignores taps.
Minify JavaScript
164 KiB164 KiB could be saved by minifying JavaScript.
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 48 ms
48 msYour server sent the HTML in 48 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 CLS: 0.52
0.52For real visitors the layout shifts by 0.52 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 18.8 s
18.8 sYour largest element takes 18.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “0 0 Ridicare personala: Auchan Titan Top Oferte LEGO si Juc…”.
Time to Interactive: 21.0 s
21.0 sThe page becomes fully interactive after 21.0 s. Good is under 3.8 s.
Speed Index: 8.8 s
8.8 sVisually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.279
0.279The layout shifts by 0.279 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 428 ms
428 msReal visitors wait 428 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 280 ms to 382 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 536 ms
536 msScripts block taps and scrolling for 536 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 3.2 MB in 309 requests
3.2 MBYour homepage downloads 3.2 MB in 309 requests on a phone: scripts 1.8 MB (138), images 578 KiB (38) and other files 360 KiB (117). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
316 KiB2 images are downloaded at several times the size a phone draws them, for example 16db1d59-a082-4336-9b4b-62021dec2554___b5ec94ff47387db7fee59 at 2,050 px wide, shown at 374 px. Resized copies would save about 316 KiB.
1 image in older formats
1 image (38 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.9 g of CO₂ per visit
0.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.91 g of CO₂e: 109.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
17 buttons without a name
17 buttons have no accessible name, so screen readers announce just “button”.
Images must have alternative text (8 elements)
Images must have alternative text: 8 elements on the page fail this check, rated critical by axe-core.
ARIA commands must have an accessible name (8 elements)
ARIA commands must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (8 elements)
Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
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 (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (9 elements).
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
789 internal links, 7 external
The homepage links to 789 pages on auchan.ro and 7 external pages.
6 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Comanda online de la hipermarketul Auchan: fructe proaspete, bauturi, articole de menaj si multe altele. Livrare rapida…”.
Title: 51 characters
Your title is a healthy 51 characters: “Auchan... si viata se schimba! | Hipermarket online”.
Canonical URL set
The canonical URL is https://www.auchan.ro/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.auchan.ro/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.auchan.ro/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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,926 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://www.auchan.ro/black-friday has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.auchan.ro/brutarie-cofetarie-gastro/c, https://www.auchan.ro/dietetic-si-international/c and https://www.auchan.ro/ingrijire-personala-si-cosmetice/c took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “window.getSnowflakesConfig is not a function”.
2 checks passed
Tap targets are thumb-sized
58 of 62 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 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 447 words of copy
The homepage carries about 447 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Pet Shop”, “LEGO Shop” and “[email protected]”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 auchan.ro, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on auchan.ro, including 24 speed issues, 2 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.