Website review, no card needed
starrett.com.br website review
Visit site (opens in a new tab)Reviewed 27 October 202638 issues · 81 checks
This review found 38 issues worth fixing on starrett.com.br, 16 of them high impact, across 81 checks. The most urgent: render-blocking 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
71C- #94,908 of 117,269 reviewed websitesbeats 16%
- #58,720 of 66,888 online storesbeats 10%
- #417 of 711 Magento storesbeats 38%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.5 s |
| Jun 13, 2026 | 4.5 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.5 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 5.0 s |
| Oct 24, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 184 ms |
| May 16, 2026 | 180 ms |
| May 23, 2026 | 177 ms |
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 176 ms |
| Jun 20, 2026 | 181 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 192 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 192 ms |
| Jul 25, 2026 | 198 ms |
| Aug 1, 2026 | 204 ms |
| Aug 8, 2026 | 212 ms |
| Aug 15, 2026 | 225 ms |
| Aug 22, 2026 | 223 ms |
| Aug 29, 2026 | 220 ms |
| Sep 5, 2026 | 218 ms |
| Sep 12, 2026 | 221 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 218 ms |
| Oct 3, 2026 | 222 ms |
| Oct 10, 2026 | 217 ms |
| Oct 17, 2026 | 232 ms |
| Oct 24, 2026 | 232 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
0.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.4 s
6.3 s
7.2 s
Speed
Render-blocking requests
2.8 s55 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Use efficient cache lifetimes
1.4 s · 1.1 MB123 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
3,510 HTML elements
The page has 3,510 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 69). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 155 KiBAbout 155 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.
Minify JavaScript
300 ms · 77 KiB77 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 259 ms. During a long task the page ignores taps.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 435 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
150 ms · 153 KiBAbout 153 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
150 ms · 65 KiB3 images could be 65 KiB 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.
4 third-party services on the page
4 third-party services load with your homepage (dinamize.com, Other Google APIs/SDKs and Optanon and others), adding 177 KiB and 49 ms of main-thread time.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 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: 31 ms
31 msYour server sent the HTML in 31 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: 5.2 s
5.2 sReal visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.0 s
5.0 sReal visitors see the first content after 5.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.4 s
3.4 sReal visitors wait 3.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “M1 Starrett”.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 7.8 s
7.8 sThe page becomes fully interactive after 7.8 s. Good is under 3.8 s.
Real-user INP: 297 ms
297 msReal visitors wait 297 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 184 ms to 232 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.105
0.105The layout shifts by 0.105 while loading, so content jumps under the reader's thumb. Good is under 0.1.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Total Blocking Time: 198 ms
198 msScripts block the page for only 198 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.9 MB in 133 requests
2.9 MBYour homepage downloads 2.9 MB in 133 requests on a phone: fonts 1.3 MB (5), images 776 KiB (27) and scripts 489 KiB (55). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Poda_png.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).
1 image below the first screen load straight away
1 image further down the page (63 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 97.1 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
Images must have alternative text (3 elements)
Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.
40 text elements with low contrast
40 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (116 elements)
All page content should be contained by landmarks: 116 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.
1 checks passed
50 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: 50 passed and 4 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 canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
485 internal links, 17 external
The homepage links to 485 pages on starrett.com.br and 17 external pages.
5 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “A qualidade que você confia, agora na nossa loja oficial Starrett. Líderes em soluções de corte e medição, confiança e …”.
One H1 headline
Your main headline reads: “Starrett”.
Title: 46 characters
Your title is a healthy 46 characters: “Starrett® | Ofertas Exclusivas na Loja Oficial”.
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://starrett.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://starrett.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.
2 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 (2,409 words), so crawlers that don't run JavaScript still read it.
Other pages
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://starrett.com.br/serra/serra-copo, whose canonical is https://starrett.com.br/serras/serra-copo. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 190 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.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://starrett.com.br' has been bloc…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
50 of 52 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.
Thin social proof
Social proof on the homepage: 3 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 1,123 words of copy
The homepage carries about 1,123 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and PostHog.
Privacy and tracking
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 starrett.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
- Framework
- jQuery
- E-commerce
- Magento
- Analytics
- Google Analytics | Google Tag Manager | PostHog
- Hosting
- Sucuri
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 starrett.com.br, including 20 speed issues, 3 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.