Website review, no card needed
italika.mx website review
Visit site (opens in a new tab)Reviewed 26 October 202653 issues · 95 checks
This review found 53 issues worth fixing on italika.mx, 21 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 193 ms |
| May 16, 2026 | 191 ms |
| May 23, 2026 | 189 ms |
| May 30, 2026 | 191 ms |
| Jun 6, 2026 | 193 ms |
| Jun 13, 2026 | 194 ms |
| Jun 20, 2026 | 195 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 192 ms |
| Jul 11, 2026 | 192 ms |
| Jul 18, 2026 | 190 ms |
| Jul 25, 2026 | 191 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 195 ms |
| Aug 15, 2026 | 198 ms |
| Aug 22, 2026 | 209 ms |
| Aug 29, 2026 | 222 ms |
| Sep 5, 2026 | 231 ms |
| Sep 12, 2026 | 238 ms |
| Sep 19, 2026 | 239 ms |
| Sep 26, 2026 | 235 ms |
| Oct 3, 2026 | 230 ms |
| Oct 10, 2026 | 224 ms |
| Oct 17, 2026 | 222 ms |
| Oct 24, 2026 | 224 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
Use efficient cache lifetimes
6.8 s · 1.8 MB166 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Render-blocking requests
6.0 s26 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.0 s.
Reduce unused JavaScript
1.9 s · 1.0 MBAbout 1.0 MB 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.
Google Tag Manager adds 1.6 s
1.6 sGoogle Tag Manager costs a phone 1.6 s of main-thread work and 1.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.
Reduce unused CSS
1.1 s · 234 KiBAbout 234 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 29
29/100Your mobile performance score is 29 (desktop: 52). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.1 s
A phone's processor spends 7.1 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,305 HTML elements
The page has 3,305 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
4.6 MB5 images could be 4.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and refaccionesitalika.com.mx and others), adding 14.1 MB and 2.9 s of main-thread time.
refaccionesitalika.com.mx adds 209 ms
209 msrefaccionesitalika.com.mx costs a phone 209 ms of main-thread work and 12.1 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.
Facebook adds 348 ms
348 msFacebook costs a phone 348 ms of main-thread work and 343 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 CSS
300 ms · 54 KiB54 KiB could be saved by minifying CSS.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 299 ms. During a long task the page ignores taps.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Minify JavaScript
150 ms · 37 KiB37 KiB could be saved by minifying JavaScript.
Legacy JavaScript
61 KiBPolyfills for old browsers add 61 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: 94 ms
94 msYour server sent the HTML in 94 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 LCP: 6.5 s
6.5 sReal visitors wait 6.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 10.4 s
10.4 sThe first text or image appears after 10.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 18.5 s
18.5 sYour largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide image”.
Time to Interactive: 28.8 s
28.8 sThe page becomes fully interactive after 28.8 s. Good is under 3.8 s.
Speed Index: 12.5 s
12.5 sVisually, the page fills in at 12.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Real-user TTFB: 945 ms
945 msReal visitors wait 945 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 193 ms to 224 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 188 ms
188 msReal visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.085
0.085The layout barely moves while loading (CLS 0.085, good is under 0.1).
Images and page weight
Page weight: 16.4 MB in 319 requests
16.4 MBYour homepage downloads 16.4 MB in 319 requests on a phone: images 12.4 MB (90), scripts 2.9 MB (168) and fonts 831 KiB (2). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 7.4 MB together. On a phone connection a single image that size takes seconds.
17 images in older formats
17 images (9.3 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.
6 images far larger than shown
217 KiB6 images are downloaded at several times the size a phone draws them, for example DobleProposito-Banner.webp at 1,200 px wide, shown at 358 px. Resized copies would save about 217 KiB.
1 image below the first screen load straight away
1 image further down the page (33 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.6 g of CO₂ per visit
4.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.65 g of CO₂e: 558.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (8 elements).
2 checks passed
Every image has alt text
All 107 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (14 characters)
Your title is only 14 characters: “Tienda Italika”. 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.
27 links crawlers can't follow
27 links have no real href, so search engines can't follow them.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
98 internal links, 22 external
The homepage links to 98 pages on italika.mx and 22 external pages.
5 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “Compra la moto de tus sueños en nuestra tienda en línea Italika. Aprovecha las diferentes formas de pago.”.
One H1 headline
Your main headline reads: “ITALIKA | Motocicletas, Cotizaciones y Tienda Oficial en México”.
Canonical URL set
The canonical URL is https://www.italika.mx/.
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.italika.mx/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 (554 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.italika.mx/llms.txt (12 KiB, 103 links), a plain-text guide to the site for AI tools.
Other pages
16 pages share a title
/, https://www.italika.mx/refacciones, https://www.italika.mx/servicios, https://www.italika.mx/promociones-motos, https://www.italika.mx/quienes-somos and https://www.italika.mx/motos/trabajo and 10 others all use the title “Tienda Italika”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages share a meta description
https://www.italika.mx/servicios, https://www.italika.mx/promociones-motos, https://www.italika.mx/quienes-somos, https://www.italika.mx/motos/trabajo, https://www.italika.mx/motos/motoneta and https://www.italika.mx/motos/linea-z and 8 others use the same meta description. A description written for each page earns more clicks.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.italika.mx/motos/Cuatrimoto, whose canonical is https://www.italika.mx/motos/cuatrimoto. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://www.italika.mx/refacciones, https://www.italika.mx/servicios, https://www.italika.mx/promociones-motos, https://www.italika.mx/quienes-somos, https://www.italika.mx/motos/trabajo and https://www.italika.mx/motos/motoneta and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://www.italika.mx/refacciones, https://www.italika.mx/servicios, https://www.italika.mx/promociones-motos, https://www.italika.mx/quienes-somos, https://www.italika.mx/motos/trabajo and https://www.italika.mx/motos/motoneta and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 pages slow to respond
https://www.italika.mx/motos/caferacer, https://www.italika.mx/motos/Crossover and https://www.italika.mx/motos/morbidelli took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
10 small tap targets
10 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 third-party cookies
4 third-party cookies are 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 “Unexpected token '('”.
9 distorted images
9 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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.
Thin social proof
Social proof on the homepage: 10 trust badges. 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 306 words of copy
The homepage carries about 306 words of visible text.
2 checks passed
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 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.
36 cookies set on arrival
36Opening the homepage sets 36 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.
37 other companies contacted
Loading the homepage contacts 37 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 italika.mx, 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
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
Company
- Founded
- 2004
- Headquarters
- Toluca de Lerdo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on italika.mx, including 23 speed issues, 4 SEO issues and 4 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.