Website review, no card needed
chevignon.com.co website review
Visit site (opens in a new tab)Reviewed 30 October 202647 issues · 87 checks
This review found 47 issues worth fixing on chevignon.com.co, 16 of them high impact, across 87 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 4.0 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 294 ms |
| May 16, 2026 | 295 ms |
| May 23, 2026 | 299 ms |
| May 30, 2026 | 300 ms |
| Jun 6, 2026 | 294 ms |
| Jun 13, 2026 | 293 ms |
| Jun 20, 2026 | 292 ms |
| Jun 27, 2026 | 291 ms |
| Jul 4, 2026 | 293 ms |
| Jul 11, 2026 | 299 ms |
| Jul 18, 2026 | 302 ms |
| Jul 25, 2026 | 305 ms |
| Aug 1, 2026 | 315 ms |
| Aug 8, 2026 | 320 ms |
| Aug 15, 2026 | 341 ms |
| Aug 22, 2026 | 355 ms |
| Aug 29, 2026 | 357 ms |
| Sep 5, 2026 | 362 ms |
| Sep 12, 2026 | 362 ms |
| Sep 19, 2026 | 367 ms |
| Sep 26, 2026 | 367 ms |
| Oct 3, 2026 | 361 ms |
| Oct 10, 2026 | 358 ms |
| Oct 17, 2026 | 360 ms |
| Oct 24, 2026 | 362 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.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.3 s
6.2 s
7.1 s
Speed
Reduce unused JavaScript
3.6 s · 980 KiBAbout 980 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
vtexassets.com adds 1.1 s
1.1 svtexassets.com costs a phone 1.1 s of main-thread work and 2.8 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: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 3.0 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 TikTok and others), adding 4.7 MB and 2.6 s of main-thread time.
Improve image delivery
450 ms · 1.0 MB12 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
600 ms · 412 KiB26 files are served with short cache lifetimes, so returning visitors download them again (412 KiB).
Google Tag Manager adds 809 ms
809 msGoogle Tag Manager costs a phone 809 ms of main-thread work and 887 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.
Reduce unused CSS
600 ms · 175 KiBAbout 175 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.
Legacy JavaScript
300 ms · 140 KiBPolyfills for old browsers add 140 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
400 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 306 ms. During a long task the page ignores taps.
2,096 HTML elements
The page has 2,096 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Unpkg adds 60 ms
60 msUnpkg costs a phone 60 ms of main-thread work and 312 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.
Minify JavaScript
150 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 36 ms
36 msYour server sent the HTML in 36 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.98
0.98For real visitors the layout shifts by 0.98 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 21.5 s
21.5 sYour largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s.
Time to Interactive: 28.9 s
28.9 sThe page becomes fully interactive after 28.9 s. Good is under 3.8 s.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 352 ms
352 msReal visitors wait 352 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 294 ms to 362 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 861 ms
861 msReal visitors wait 861 ms for your server to start answering (75th percentile). Good is under 800 ms.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0.043
0.043The layout barely moves while loading (CLS 0.043, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 158 requests
5.6 MBYour homepage downloads 5.6 MB in 158 requests on a phone: scripts 2.9 MB (65), images 1.5 MB (26) and HTML 422 KiB (3). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
3 KiB2 images are downloaded at several times the size a phone draws them, for example 063b18bc-9a01-4833-9cfa-5c438582c549___b4bae4c4a8fd795c85874 at 800 px wide, shown at 266 px. Resized copies would save about 3 KiB.
1 image in older formats
1 image (36 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 1.6 g of CO₂ per visit
1.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 189.7 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
Hidden but focusable
8 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 47 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.
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.
133 internal links, 12 external
The homepage links to 133 pages on chevignon.com.co and 12 external pages.
6 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “La tienda de ropa online de Chevignon Colombia tiene jeans, camisas, camisetas, chaquetas y más prendas para hombre, mu…”.
One H1 headline
Your main headline reads: “En Chevignon nos dedicamos a crear piezas atemporales que celebran una historia compartida.”.
Title: 42 characters
Your title is a healthy 42 characters: “Tienda de ropa online | Chevignon Colombia”.
Canonical URL set
The canonical URL is https://www.chevignon.com.co/.
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.chevignon.com.co/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.
No llms.txt
There is no https://www.chevignon.com.co/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 (623 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a title
https://www.chevignon.com.co/ropa-hombre/polos, https://www.chevignon.com.co/ropa-hombre/zapatos and https://www.chevignon.com.co/ropa-hombre/camisas have no <title>, so Google invents the link text in results.
3 pages without a meta description
https://www.chevignon.com.co/ropa-hombre/polos, https://www.chevignon.com.co/ropa-hombre/zapatos and https://www.chevignon.com.co/ropa-hombre/camisas have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.chevignon.com.co/new-arrivals-denim and https://www.chevignon.com.co/new-arrivals-accesorios use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://www.chevignon.com.co/ropa-hombre/polos, https://www.chevignon.com.co/ropa-hombre/zapatos and https://www.chevignon.com.co/ropa-hombre/camisas have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://www.chevignon.com.co/new-arrivals-hombre, https://www.chevignon.com.co/new-arrivals-mujer, https://www.chevignon.com.co/new-arrivals-denim, https://www.chevignon.com.co/new-arrivals-accesorios, https://www.chevignon.com.co/ropa-hombre/polos and https://www.chevignon.com.co/ropa-hombre/zapatos took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 91 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.
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.
Best practices
8 small tap targets
8 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
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 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 348 words of copy
The homepage carries about 348 words of visible text.
3 checks passed
Social proof on the page
Social proof on the homepage: 16 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 mores (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.
25 cookies set on arrival
25Opening the homepage sets 25 cookies, 2 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.
40 other companies contacted
Loading the homepage contacts 40 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 chevignon.com.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- Analytics
- Google Tag Manager
- Hosting
- Enflow
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on chevignon.com.co, including 27 speed issues, 3 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.