Website review, no card needed

insiderstore.com.br logo

insiderstore.com.br website review

Visit site (opens in a new tab)Reviewed 19 November 202646 issues · 84 checks

This review found 46 issues worth fixing on insiderstore.com.br, 17 of them high impact, across 84 checks. The most urgent: main-thread work: 14.2 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.5 s2.1 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.4 s
Nov 7, 20262.4 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
993 ms230 msMay 30Nov 14318 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026412 ms
Jun 6, 2026536 ms
Jun 13, 2026720 ms
Jun 20, 2026771 ms
Jun 27, 2026751 ms
Jul 4, 2026732 ms
Jul 11, 2026726 ms
Jul 18, 2026723 ms
Jul 25, 2026727 ms
Aug 1, 2026724 ms
Aug 8, 2026753 ms
Aug 15, 2026777 ms
Aug 22, 2026805 ms
Aug 29, 2026841 ms
Sep 5, 2026876 ms
Sep 12, 2026905 ms
Sep 19, 2026610 ms
Sep 26, 2026491 ms
Oct 3, 2026421 ms
Oct 10, 2026369 ms
Oct 17, 2026353 ms
Oct 24, 2026349 ms
Oct 31, 2026341 ms
Nov 7, 2026331 ms
Nov 14, 2026318 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 insiderstore.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. insiderstore.com.br at 1.2 s1.2 s
  2. insiderstore.com.br at 2.3 s2.3 s
  3. insiderstore.com.br at 3.5 s3.5 s
  4. insiderstore.com.br at 4.7 s4.7 s
  5. insiderstore.com.br at 5.8 s5.8 s
  6. insiderstore.com.br at 7.0 s7.0 s
  7. insiderstore.com.br at 8.2 s8.2 s
  8. insiderstore.com.br at 9.3 s9.3 s

Speed

13 to fix37
  • Main-thread work: 14.2 s

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

  • Render-blocking requests

    1.0 s

    17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

  • Mobile performance score: 37

    37/100

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

  • 5,368 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 2.3 MB and 2.4 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1.1 MB

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

  • Google Tag Manager adds 816 ms

    816 ms

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

  • Use efficient cache lifetimes

    386 KiB

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

  • Shopify adds 307 ms

    307 ms

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

  • Clarity adds 285 ms

    285 ms

    Clarity costs a phone 285 ms of main-thread work and 32 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 271 ms. During a long task the page ignores taps.

  • ZenDesk adds 167 ms

    167 ms

    ZenDesk costs a phone 167 ms of main-thread work and 434 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.

  • Klaviyo adds 148 ms

    148 ms

    Klaviyo costs a phone 148 ms of main-thread work and 317 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

    150 ms · 130 KiB

    About 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Duplicated JavaScript

    50 ms · 15 KiB

    15 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

  • Legacy JavaScript

    39 KiB

    Polyfills for old browsers add 39 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.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

11 to fix33
  • 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.

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 38.9 s

    38.9 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user INP: 337 ms

    337 ms

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 5 images without width and height

    5 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-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Tap response (INP) got 32% faster for real visitors

    -32%

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

  • Cumulative Layout Shift: 0.043

    0.043

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

Images and page weight

2 to fix69
  • Page weight: 6.5 MB in 565 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 565 requests on a phone: scripts 3.6 MB (188), other files 1.7 MB (259) and images 455 KiB (36). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    C1B1_de6da0ce-e405-4c01-a3f1-59cb19c5bd5f.png 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).

  • 2 images below the first screen load straight away

    2 images further down the page (52 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.86 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8390
  • 8 buttons without a name

    8 buttons have no accessible name, so screen readers announce just “button”.

  • 7 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 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.

  • 14 links without text

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

2 checks passed
  • Every image has alt text

    All 36 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9279
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Confira peças essenciais com tecnologia têxtil | Insider – Insider”.

  • 31 links crawlers can't follow

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

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: url is not an absolute URL ("www.insiderstore.com.br")”.

  • No XML sitemap

    No XML sitemap at https://www.insiderstore.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at insiderstore.com.br/robots.txt, the first file search crawlers ask for.

  • 279 internal links, 5 external

    The homepage links to 279 pages on insiderstore.com.br and 5 external pages.

4 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “A INSIDER cria peças tecnológicas, sustentáveis e essencialmente funcionais. Confira a inovação em camisetas, underwear…”.

  • One H1 headline

    Your main headline reads: “ROUPAS TECNOLÓGICAS: TECIDOS INTELIGENTES E DESIGN FUNCIONAL”.

  • Canonical URL set

    The canonical URL is https://www.insiderstore.com.br/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix81
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.insiderstore.com.br/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
  • Text is in the HTML

    Your server sends the page's text in the HTML (2,586 words), so crawlers that don't run JavaScript still read it.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

4 to fixGoogle 5074
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=15338849&tm=gtm002&Ver=2&mid=3f42d640-0468-4293-a81f-e30ba79be64e&bo=5&sid=dbf9a700e43311f1baf003daf2a18629&vid=dbf9e460e43311f196b499add59a5e5e&vids=1&msclkid=N&pi=91.

  • 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.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “rs_dataplane_config cookie not found.”.

  • Missing source maps

    Large scripts ship without source maps.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    62 of 73 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 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.

  • 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 731 words of copy

    The homepage carries about 731 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop The Creator Look Masculino”, “Shop The Creator Look Feminino” and “SHOP BEST-SELLERS”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Hotjar.

Privacy and tracking

1 to fix
  • 12 trackers load before any consent

    12

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

  • 46 cookies set on arrival

    46

    Opening the homepage sets 46 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.

  • 72 other companies contacted

    Loading the homepage contacts 72 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 insiderstore.com.br, 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 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Seo Manager Venntov · Insider · Microsoft Clarity · Gsc Countdown Timer · Klaviyo Email Marketing Sms · Sra Google Analytics 4 Ga4 · Avada Seo Suite · Gdpr Cookie Consent · Sliderule Analytics · Productiondeployment · Pagbrasil App Companion · rakutenadvertising.io · activehosted.com · addons.business · bogos.io

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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
São Paulo

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on insiderstore.com.br, including 24 speed issues, 5 SEO issues and 3 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