Website review, no card needed
creveleurope.com website review
Visit site (opens in a new tab)Reviewed 9 November 202639 issues · 80 checks
This review found 39 issues worth fixing on creveleurope.com, 12 of them high impact, across 80 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
83B- #28,699 of 126,458 reviewed websitesbeats 72%
- #18,581 of 70,479 online storesbeats 67%
- #17,979 of 63,972 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 81 ms |
| May 30, 2026 | 83 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 79 ms |
| Jun 20, 2026 | 78 ms |
| Jun 27, 2026 | 85 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 85 ms |
| Jul 18, 2026 | 86 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 72 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 77 ms |
| Aug 22, 2026 | 81 ms |
| Aug 29, 2026 | 86 ms |
| Sep 5, 2026 | 85 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 91 ms |
| Sep 26, 2026 | 91 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 84 ms |
| Oct 24, 2026 | 88 ms |
| Oct 31, 2026 | 107 ms |
| Nov 7, 2026 | 110 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
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.3 s
Speed
Reduce unused JavaScript
1.9 s · 740 KiBAbout 740 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Improve image delivery
1.1 s · 614 KiB16 images could be 614 KiB 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.
Render-blocking requests
1.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (ContentSquare, Google Tag Manager and Shopify and others), adding 1.3 MB and 833 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 843 ms. During a long task the page ignores taps.
Reduce unused CSS
600 ms · 104 KiBAbout 104 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
ContentSquare adds 288 ms
288 msContentSquare costs a phone 288 ms of main-thread work and 380 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.
Shopify adds 202 ms
202 msShopify costs a phone 202 ms of main-thread work and 378 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.
1,553 HTML elements
The page has 1,553 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 207 KiB7 files are served with short cache lifetimes, so returning visitors download them again (207 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
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: 7 ms
7 msYour server sent the HTML in 7 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.
Largest Contentful Paint: 13.2 s
13.2 sYour largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 15.4 s
15.4 sThe page becomes fully interactive after 15.4 s. Good is under 3.8 s.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 651 ms
651 msScripts block taps and scrolling for 651 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 81 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
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.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 137 ms
137 msReal visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
2 images over 500 KB
2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
973 KiB7 images are downloaded at several times the size a phone draws them, for example crevel-ddlm-p-zmango.webp at 640 px wide, shown at 157 px. Resized copies would save about 973 KiB.
Page weight: 3.7 MB in 239 requests
3.7 MBYour homepage downloads 3.7 MB in 239 requests on a phone: scripts 1.5 MB (79), images 1.0 MB (31) and other files 768 KiB (104). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (2.6 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.
3 images below the first screen load straight away
3 images further down the page (162 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 126.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
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.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 74 images in the HTML carry an alt attribute.
45 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: 45 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
186 internal links, 12 external
The homepage links to 186 pages on creveleurope.com and 12 external pages.
8 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Crevel serves over 400 loyal customers as the leading distributor of authentic Mexican and American products for foodse…”.
One H1 headline
Your main headline reads: “Building international FMCG brands in Europe.”.
Title: 57 characters
Your title is a healthy 57 characters: “B2B distributor of Mexican and American products | Crevel”.
Canonical URL set
The canonical URL is https://www.creveleurope.com/.
Structured data in place
Structured data found: WebSite.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.creveleurope.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 (1,170 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.creveleurope.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 linked pages hidden from search
https://www.creveleurope.com/collections/american-candy, https://www.creveleurope.com/collections/american-drinks, https://www.creveleurope.com/collections/american-snacks, https://www.creveleurope.com/collections/american-selection-food-grocery, https://www.creveleurope.com/collections/mexican-candy and https://www.creveleurope.com/collections/mexican-drinks and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
9 pages share 4 titles
https://www.creveleurope.com/collections/american-candy, https://www.creveleurope.com/collections/mexican-candy and https://www.creveleurope.com/collections/asian-candy all use the title “Candy from Around the World | Crevel”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.creveleurope.com/collections/american-non-food and https://www.creveleurope.com/collections/asian-food-grocery have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages share a meta description
https://www.creveleurope.com/collections/american-candy, https://www.creveleurope.com/collections/mexican-candy and https://www.creveleurope.com/collections/asian-candy use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
24 small tap targets
24 of 40 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 “Uncaught Error: Contentsquare tag 392960 skipped: another Contentsquare tag already runs”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: “3,500+ customers”. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 828 words of copy
The homepage carries about 828 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Shop the collection”.
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “Shop the collection” and “My order”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Klaviyo (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
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.
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 creveleurope.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Smart Seo · Hotjar Install · Wiser Upsell Cross Sell · Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · hubapi.com · magefan.top
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on creveleurope.com, including 21 speed 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.