Website review, no card needed
adquim.com website review
Visit site (opens in a new tab)Reviewed 19 October 202635 issues · 77 checks
This review found 35 issues worth fixing on adquim.com, 10 of them high impact, across 77 checks. The most urgent: page weight: 41.3 MB in 317 requests. 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
75C- #77,476 of 117,602 reviewed websitesbeats 30%
- #49,603 of 66,923 online storesbeats 22%
- #46,889 of 61,018 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.8 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
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Clarity and Shopify and others), adding 39.6 MB and 1.1 s of main-thread time.
Shopify adds 35 ms
35 msShopify costs a phone 35 ms of main-thread work and 38.4 MB 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.
Reduce unused JavaScript
640 ms · 606 KiBAbout 606 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 640 ms faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61 (desktop: 79). Pages that score under 90 lose visitors before the first paint.
YouTube adds 676 ms
676 msYouTube costs a phone 676 ms of main-thread work and 993 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.
Clarity adds 334 ms
334 msClarity costs a phone 334 ms of main-thread work and 28 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.
Use efficient cache lifetimes
300 ms · 12 KiB3 files are served with short cache lifetimes, so returning visitors download them again (12 KiB).
Render-blocking requests
150 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 132 ms. During a long task the page ignores taps.
Reduce unused CSS
126 KiBAbout 126 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
83 KiB1 image could be 83 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 16.2 s
16.2 sVisually, the page fills in at 16.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (4.7 s).
Time to Interactive: 17.4 s
17.4 sThe page becomes fully interactive after 17.4 s. Good is under 3.8 s.
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.
Total Blocking Time: 205 ms
205 msScripts block taps and scrolling for 205 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
1 checks passed
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 41.3 MB in 317 requests
41.3 MBYour homepage downloads 41.3 MB in 317 requests on a phone: media 38.3 MB (4), scripts 1.2 MB (45) and other files 1.1 MB (197). Under 2 MB keeps phones on slow connections fast.
About 11.7 g of CO₂ per visit
11.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 11.69 g of CO₂e: 1403.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
22 text elements with low contrast
22 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
7 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
43 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: 43 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (6 characters)
Your title is only 6 characters: “Adquim”. 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.
Meta description is short (6 characters)
Your meta description is only 6 characters: “Adquim”. 70 to 160 characters is enough to sell the click.
36 internal links, 6 external
The homepage links to 36 pages on adquim.com and 6 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Adquim”.
Canonical URL set
The canonical URL is https://adquim.com/.
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://adquim.com/sitemap.xml.
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (553 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://adquim.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://adquim.com/products/adblue-%C2%AE-5-litros and https://adquim.com/products/adblue-bidon-10-lts use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://adquim.com/products/adblue-%C2%AE-5-litros, whose canonical is https://adquim.com/products/adblue-%c2%ae-5-litros. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://adquim.com/blogs/news has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 small tap targets
5 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to script at 'https://cdn.ecomposer.app/vendors/js/jquery.min.js' from origin 'https://adquim.com' has been bloc…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
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 525 words of copy
The homepage carries about 525 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Microsoft Clarity (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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 1 of them by other companies (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.
15 other companies contacted
Loading the homepage contacts 15 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 adquim.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
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on adquim.com, including 13 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.