Website review, no card needed
dportenis.mx website review
Visit site (opens in a new tab)Reviewed 31 October 202638 issues · 79 checks
This review found 38 issues worth fixing on dportenis.mx, 18 of them high impact, across 79 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
57FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.8 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 455 ms |
| May 16, 2026 | 442 ms |
| May 23, 2026 | 432 ms |
| May 30, 2026 | 422 ms |
| Jun 6, 2026 | 417 ms |
| Jun 13, 2026 | 414 ms |
| Jun 20, 2026 | 414 ms |
| Jun 27, 2026 | 415 ms |
| Jul 4, 2026 | 417 ms |
| Jul 11, 2026 | 427 ms |
| Jul 18, 2026 | 446 ms |
| Jul 25, 2026 | 462 ms |
| Aug 1, 2026 | 479 ms |
| Aug 8, 2026 | 488 ms |
| Aug 15, 2026 | 481 ms |
| Aug 22, 2026 | 484 ms |
| Aug 29, 2026 | 482 ms |
| Sep 5, 2026 | 484 ms |
| Sep 12, 2026 | 482 ms |
| Sep 19, 2026 | 478 ms |
| Sep 26, 2026 | 489 ms |
| Oct 3, 2026 | 493 ms |
| Oct 10, 2026 | 492 ms |
| Oct 17, 2026 | 492 ms |
| Oct 24, 2026 | 475 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
2.0 s
4.0 s
5.9 s
7.9 s
9.9 s
11.9 s
13.9 s
15.8 s
Speed
Reduce unused JavaScript
2.3 s · 961 KiBAbout 961 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Use efficient cache lifetimes
1.3 s · 1.8 MB52 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Main-thread work: 13.9 s
A phone's processor spends 13.9 s on main-thread work while loading, 10.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 14
14/100Your mobile performance score is 14. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,291 HTML elements
The page has 5,291 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
600 ms · 1.6 MB49 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 5.7 MB and 759 ms of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 674 ms. During a long task the page ignores taps.
Google Tag Manager adds 496 ms
496 msGoogle Tag Manager costs a phone 496 ms of main-thread work and 547 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.
cloudfront.net adds 1 ms
1 mscloudfront.net costs a phone 1 ms of main-thread work and 4.5 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.
Legacy JavaScript
200 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
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 INP: 1.1 s
1.1 sReal visitors wait 1.1 s for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.67
0.67For real visitors the layout shifts by 0.67 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 11.1 s
11.1 sYour largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “F1 Generico”.
Speed Index: 16.5 s
16.5 sVisually, the page fills in at 16.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 5.3 s
5.3 sScripts block taps and scrolling for 5.3 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 25.2 s
25.2 sThe page becomes fully interactive after 25.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.477
0.477The layout shifts by 0.477 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
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.
145 images without width and height
145 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 455 ms to 475 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 7.5 MB in 527 requests
7.5 MBYour homepage downloads 7.5 MB in 527 requests on a phone: images 4.5 MB (178), scripts 2.0 MB (30) and other files 591 KiB (308). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
mobile-F1-Generico-dportenis.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
12 images in older formats
12 images (503 KiB) 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.
7 images far larger than shown
172 KiB7 images are downloaded at several times the size a phone draws them, for example tendencias-AS-Novablast-dportenis.webp at 1,280 px wide, shown at 350 px. Resized copies would save about 172 KiB.
About 2.1 g of CO₂ per visit
2.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.12 g of CO₂e: 254.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
35 text elements with low contrast
35 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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 51 images in the HTML carry an alt attribute.
22 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 24 WCAG 2.2 A/AA and best-practice rules on the phone render: 22 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
61 internal links, 7 external
The homepage links to 61 pages on dportenis.mx and 7 external pages.
7 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Visita dportenis y encuentra tenis de hombre y mujer, ropa deportiva y accesorios de marcas top. Mejora tu rendimiento …”.
One H1 headline
Your main headline reads: “dportenis: tenis, ropa y accesorios deportivos”.
Title: 54 characters
Your title is a healthy 54 characters: “Tenis de hombre, mujer y ropa deportiva | dportenis.mx”.
Canonical URL set
The canonical URL is https://www.dportenis.mx/.
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.dportenis.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.
Some text only appears after JavaScript runs
32%The HTML your server sends has 274 of the 860 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.dportenis.mx/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.
1 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.
Other pages
3 pages without an H1
https://www.dportenis.mx/buscar, https://www.dportenis.mx/coleccion-otono-meses-sin-intereses-nino and https://www.dportenis.mx/adidas-dia-de-muertos have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.dportenis.mx/iniciar-sesion and https://www.dportenis.mx/buscar 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.
1 page slow to respond
https://www.dportenis.mx/marcas-dportenis/hoka took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
209 of 211 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 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 860 words of copy
The homepage carries about 860 words of visible text.
1 checks passed
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (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 dportenis.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
- Next.js
- Hosting
- AWS
Company
- Founded
- 1987
- Headquarters
- Mazatlán
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on dportenis.mx, including 22 speed issues, 1 SEO issue 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.