Website review, no card needed

highstreet.com.mx logo

highstreet.com.mx website review

Visit site (opens in a new tab)Reviewed 25 October 202647 issues · 94 checks

This review found 47 issues worth fixing on highstreet.com.mx, 18 of them high impact, across 94 checks. The most urgent: clarity adds 4.5 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.6 s2.2 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.6 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
297 ms229 msMay 2Oct 17237 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026253 ms
May 9, 2026254 ms
May 16, 2026259 ms
May 23, 2026257 ms
May 30, 2026257 ms
Jun 6, 2026271 ms
Jun 13, 2026272 ms
Jun 20, 2026281 ms
Jun 27, 2026288 ms
Jul 4, 2026288 ms
Jul 11, 2026289 ms
Jul 18, 2026278 ms
Jul 25, 2026267 ms
Aug 1, 2026259 ms
Aug 8, 2026258 ms
Aug 15, 2026259 ms
Aug 22, 2026257 ms
Aug 29, 2026254 ms
Sep 5, 2026250 ms
Sep 12, 2026246 ms
Sep 19, 2026244 ms
Sep 26, 2026240 ms
Oct 3, 2026238 ms
Oct 10, 2026239 ms
Oct 17, 2026237 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

Full-page screenshot of highstreet.com.mx (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. highstreet.com.mx at 1.0 s1.0 s
  2. highstreet.com.mx at 2.1 s2.1 s
  3. highstreet.com.mx at 3.1 s3.1 s
  4. highstreet.com.mx at 4.1 s4.1 s
  5. highstreet.com.mx at 5.1 s5.1 s
  6. highstreet.com.mx at 6.2 s6.2 s
  7. highstreet.com.mx at 7.2 s7.2 s
  8. highstreet.com.mx at 8.2 s8.2 s

Speed

14 to fix39
  • Clarity adds 4.5 s

    4.5 s

    Clarity costs a phone 4.5 s of main-thread work and 29 KiB 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.

  • Main-thread work: 27.8 s

    A phone's processor spends 27.8 s on main-thread work while loading, 21.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • replocdn.com adds 1.5 s

    1.5 s

    replocdn.com costs a phone 1.5 s of main-thread work and 664 KiB 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: 39

    39/100

    Your mobile performance score is 39 (desktop: 45). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 4,158 HTML elements

    The page has 4,158 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    150 ms · 10.8 MB

    115 images could be 10.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, replocdn.com and Google Tag Manager and others), adding 10.9 MB and 7.4 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Shopify adds 74 ms

    74 ms

    Shopify costs a phone 74 ms of main-thread work and 8.6 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.

  • Use efficient cache lifetimes

    150 ms · 574 KiB

    30 files are served with short cache lifetimes, so returning visitors download them again (574 KiB).

  • Reduce unused CSS

    600 ms · 110 KiB

    About 110 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.

  • Google Tag Manager adds 568 ms

    568 ms

    Google Tag Manager costs a phone 568 ms of main-thread work and 663 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.

  • Render-blocking requests

    500 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

  • Klaviyo adds 280 ms

    280 ms

    Klaviyo costs a phone 280 ms of main-thread work and 335 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 216 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    91 KiB

    Polyfills for old browsers add 91 KiB JavaScript that modern phones do not need.

  • Minify CSS

    23 KiB

    23 KiB could be saved by minifying CSS.

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

  • 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: 20 ms

    20 ms

    Your server sent the HTML in 20 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • 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: 41.5 s

    41.5 s

    Your largest element takes 41.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 17.5 s

    17.5 s

    Visually, the page fills in at 17.5 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 68.9 s

    68.9 s

    The page becomes fully interactive after 68.9 s. Good is under 3.8 s.

  • Total Blocking Time: 1.0 s

    1.0 s

    Scripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.

  • Real-user INP: 236 ms

    236 ms

    Real visitors wait 236 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • 104 images without width and height

    104 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

  • Tap response (INP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 253 ms to 237 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

    Real visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 551 ms

    551 ms

    Real visitors wait 551 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.004

    0.004

    The layout barely moves while loading (CLS 0.004, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 24.2 MB in 579 requests

    24.2 MB

    Your homepage downloads 24.2 MB in 579 requests on a phone: images 14.3 MB (147), media 5.1 MB (1) and scripts 2.9 MB (123). Under 2 MB keeps phones on slow connections fast.

  • 40 images far larger than shown

    7.2 MB

    40 images are downloaded at several times the size a phone draws them, for example c22.jpg at 3,000 px wide, shown at 318 px. Resized copies would save about 7.2 MB.

  • 1 image over 500 KB

    c22.jpg weighs 987 KiB. On a phone connection a single image that size takes seconds.

  • 40 images below the first screen load straight away

    40 images further down the page (10.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 36 images in older formats

    36 images (8.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.

  • About 6.9 g of CO₂ per visit

    6.87 g

    By the Sustainable Web Design model, a visit to your homepage emits about 6.87 g of CO₂e: 824.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

8 to fixGoogle 8589
  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • 17 images without alt text

    17 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (50 elements)

    All page content should be contained by landmarks: 50 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.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Alternative text of images should not be repeated as text (6 elements)

    Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8587
  • Title is short (10 characters)

    Your title is only 10 characters: “HIGHSTREET”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 43 links crawlers can't follow

    43 links have no real href, so search engines can't follow them.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 387 internal links, 12 external

    The homepage links to 387 pages on highstreet.com.mx and 12 external pages.

6 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “15% off your first order. Free 24-hour shipping nationwide in Mexico. Discover all the daily new arrivals. Official HIG…”.

  • One H1 headline

    Your main headline reads: “HIGHSTREET”.

  • Canonical URL set

    The canonical URL is https://highstreet.com.mx/en-us.

  • 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://highstreet.com.mx/sitemap.xml.

AI search readiness

1 to fix88
  • 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,500 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://highstreet.com.mx/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 3 pages without a meta description

    https://highstreet.com.mx/en-us/collections/novedades-best-seller, https://highstreet.com.mx/en-us/collections/novedades-nuevos-chalecos and https://highstreet.com.mx/en-us/collections/coming-soon have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 144 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

4 to fixGoogle 6974
  • 1 broken image

    1 image failed to load on a phone, for example https://highstreet.com.mx/cdn/shop/files/ChatGPT_Image_30_jul_2026_12_30_50.png?v=1785436325&width=832.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Unexpected token ':'”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    83 of 87 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • About 965 words of copy

    The homepage carries about 965 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “The denim shop”, “Shop” and “Subscribe”.

  • 101 short forms

    101 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.

  • 36 cookies set on arrival

    36

    Opening the homepage sets 36 cookies, 3 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.

  • 56 other companies contacted

    Loading the homepage contacts 56 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 highstreet.com.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
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify Hosted;Amazon;Digital Ocean

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 highstreet.com.mx, including 22 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25