Website review, no card needed
infostore.com.br website review
Visit site (opens in a new tab)Reviewed 4 November 202662 issues · 96 checks
This review found 62 issues worth fixing on infostore.com.br, 28 of them high impact, across 96 checks. The most urgent: page weight: 16.1 MB in 250 requests. 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
54FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 3.9 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.3 s |
| Oct 24, 2026 | 4.2 s |
| Oct 31, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 303 ms |
| May 23, 2026 | 300 ms |
| May 30, 2026 | 303 ms |
| Jun 6, 2026 | 306 ms |
| Jun 13, 2026 | 319 ms |
| Jun 20, 2026 | 322 ms |
| Jun 27, 2026 | 322 ms |
| Jul 4, 2026 | 316 ms |
| Jul 11, 2026 | 314 ms |
| Jul 18, 2026 | 309 ms |
| Jul 25, 2026 | 313 ms |
| Aug 1, 2026 | 317 ms |
| Aug 8, 2026 | 315 ms |
| Aug 15, 2026 | 316 ms |
| Aug 22, 2026 | 310 ms |
| Aug 29, 2026 | 308 ms |
| Sep 5, 2026 | 307 ms |
| Sep 12, 2026 | 307 ms |
| Sep 19, 2026 | 308 ms |
| Sep 26, 2026 | 313 ms |
| Oct 3, 2026 | 311 ms |
| Oct 10, 2026 | 321 ms |
| Oct 17, 2026 | 331 ms |
| Oct 24, 2026 | 332 ms |
| Oct 31, 2026 | 335 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
1.1 s
2.2 s
3.2 s
4.3 s
5.4 s
6.5 s
7.5 s
8.6 s
Speed
Reduce initial server response time
1.6 sReduce initial server response time. Google estimates savings of 1.6 s on a phone.
Document request latency
1.6 sThe HTML itself could arrive about 1.6 s sooner: redirects, a slow server response or missing compression delay everything after it.
vtexassets.com adds 1.1 s
1.1 svtexassets.com costs a phone 1.1 s of main-thread work and 2.6 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.
Render-blocking requests
1.1 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.1 s.
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: 8.7 s
A phone's processor spends 8.7 s on main-thread work while loading, 4.6 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 CDN and Google Tag Manager and others), adding 16.5 MB and 2.9 s of main-thread time.
Reduce unused JavaScript
300 ms · 2.2 MBAbout 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Vimeo adds 160 ms
160 msVimeo costs a phone 160 ms of main-thread work and 10.4 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.
Improve image delivery
600 ms · 608 KiB15 images could be 608 KiB 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.
Use efficient cache lifetimes
350 ms · 594 KiB48 files are served with short cache lifetimes, so returning visitors download them again (594 KiB).
Google CDN adds 588 ms
588 msGoogle CDN costs a phone 588 ms of main-thread work and 2.3 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.
Google Tag Manager adds 572 ms
572 msGoogle Tag Manager costs a phone 572 ms of main-thread work and 552 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
300 ms · 134 KiBAbout 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,207 HTML elements
The page has 2,207 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 1.7 s
1.7 sYour server takes 1.7 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Legacy JavaScript
150 ms · 139 KiBPolyfills for old browsers add 139 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 223 ms. During a long task the page ignores taps.
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
4 KiB4 KiB could be saved by minifying JavaScript.
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: 4.4 s
4.4 sReal visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.1 s
4.1 sReal visitors see the first content after 4.1 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 9.9 s
9.9 sYour largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “WhatsApp”.
Time to Interactive: 37.8 s
37.8 sThe page becomes fully interactive after 37.8 s. Good is under 3.8 s.
Speed Index: 13.7 s
13.7 sVisually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Real-user INP: 335 ms
335 msReal visitors wait 335 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.102
0.102The layout shifts by 0.102 while loading, so content jumps under the reader's thumb. Good is under 0.1.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 303 ms to 335 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 16.1 MB in 250 requests
16.1 MBYour homepage downloads 16.1 MB in 250 requests on a phone: other files 10.4 MB (79), scripts 3.4 MB (90) and images 942 KiB (64). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
53 KiB2 images are downloaded at several times the size a phone draws them, for example 935f4a72-6c63-4b02-8152-bc4db5a790df___cd5784db06410abf6bb02 at 1,140 px wide, shown at 374 px. Resized copies would save about 53 KiB.
5 images below the first screen load straight away
5 images further down the page (181 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.6 g of CO₂ per visit
4.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.58 g of CO₂e: 549.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
45 text elements with low contrast
45 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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 (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (12 elements).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 10 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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 (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at infostore.com.br/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
63 internal links, 11 external
The homepage links to 63 pages on infostore.com.br and 11 external pages.
3 checks passed
Title: 39 characters
Your title is a healthy 39 characters: “Info Store | O melhor Mix em tecnologia”.
Canonical URL set
The canonical URL is https://www.infostore.com.br/.
XML sitemap found
Your XML sitemap is reachable at https://www.infostore.com.br/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.infostore.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 (849 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages are broken
Your homepage links to https://www.infostore.com.br/telefonia, https://www.infostore.com.br/games/consoles and https://www.infostore.com.br/catalogo-completo, which answer with an error. Visitors hit a dead end and search engines drop them.
2 linked pages hidden from search
https://www.infostore.com.br/771 and https://www.infostore.com.br/501 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
/ and https://www.infostore.com.br/alto-falante-jbl-tower-x-marine-250w-mt10hlw/p all use the title “Info Store | O melhor Mix em tecnologia”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.infostore.com.br/blog/hub, https://www.infostore.com.br/771, https://www.infostore.com.br/alto-falante-jbl-tower-x-marine-250w-mt10hlw/p and https://www.infostore.com.br/501 have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.infostore.com.br/marcas/rhadium, https://www.infostore.com.br/especial/ofertas-dinamicas, https://www.infostore.com.br/blog/hub and https://www.infostore.com.br/especial/area-gamer have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages slow to respond
https://www.infostore.com.br/especial/ofertas-dinamicas, https://www.infostore.com.br/blog/hub, https://www.infostore.com.br/informatica, https://www.infostore.com.br/especial/area-gamer, https://www.infostore.com.br/notebook/notebook and https://www.infostore.com.br/771 and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 51 found) and read each the way a search engine does.
2 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
27 small tap targets
27 of 59 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Warning: No Google Conversion ID is defined. Please configure it in the Google Shopping Ads App.”.
2 distorted images
2 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.
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 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 405 words of copy
The homepage carries about 405 words of visible text.
3 checks passed
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
44 other companies contacted
Loading the homepage contacts 44 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 infostore.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 62 issues on infostore.com.br, including 29 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.