Website review, no card needed
fishermans.com.br website review
Visit site (opens in a new tab)Reviewed 7 November 202641 issues · 85 checks
This review found 41 issues worth fixing on fishermans.com.br, 13 of them high impact, across 85 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
78C- #62,165 of 124,051 reviewed websitesbeats 44%
- #40,563 of 69,761 online storesbeats 36%
- #38,729 of 63,450 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 186 ms |
| May 23, 2026 | 192 ms |
| May 30, 2026 | 197 ms |
| Jun 6, 2026 | 206 ms |
| Jun 13, 2026 | 210 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 213 ms |
| Jul 4, 2026 | 210 ms |
| Jul 11, 2026 | 210 ms |
| Jul 18, 2026 | 209 ms |
| Jul 25, 2026 | 210 ms |
| Aug 1, 2026 | 220 ms |
| Aug 8, 2026 | 224 ms |
| Aug 15, 2026 | 231 ms |
| Aug 22, 2026 | 235 ms |
| Aug 29, 2026 | 235 ms |
| Sep 5, 2026 | 235 ms |
| Sep 12, 2026 | 233 ms |
| Sep 19, 2026 | 232 ms |
| Sep 26, 2026 | 234 ms |
| Oct 3, 2026 | 238 ms |
| Oct 10, 2026 | 241 ms |
| Oct 17, 2026 | 242 ms |
| Oct 24, 2026 | 241 ms |
| Oct 31, 2026 | 235 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.7 s
2.6 s
3.4 s
4.3 s
5.1 s
6.0 s
6.8 s
Speed
Reduce unused JavaScript
1.4 s · 305 KiBAbout 305 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
300 ms · 1.7 MB17 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and Google Tag Manager and others), adding 4.7 MB and 363 ms of main-thread time.
Reduce unused CSS
450 ms · 67 KiBAbout 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Fonts adds 1 ms
1 msGoogle Fonts costs a phone 1 ms of main-thread work and 3.9 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.
2,233 HTML elements
The page has 2,233 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 159 ms
159 msShopify costs a phone 159 ms of main-thread work and 572 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 195 ms. During a long task the page ignores taps.
Duplicated JavaScript
100 ms · 15 KiB15 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
16 KiB4 files are served with short cache lifetimes, so returning visitors download them again (16 KiB).
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 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.
Largest Contentful Paint: 40.4 s
40.4 sYour largest element takes 40.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 41.2 s
41.2 sThe page becomes fully interactive after 41.2 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 186 ms to 235 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 892 ms
892 msReal visitors wait 892 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 268 ms
268 msScripts block taps and scrolling for 268 ms in total while the page loads. Good is under 200 ms.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 200 ms
200 msReal visitors wait 200 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.016
0.016The layout barely moves while loading (CLS 0.016, good is under 0.1).
Images and page weight
Page weight: 8.5 MB in 233 requests
8.5 MBYour homepage downloads 8.5 MB in 233 requests on a phone: fonts 4.0 MB (8), images 2.7 MB (49) and other files 903 KiB (118). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BANNER_KITS_mobile.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).
4 images in older formats
4 images (242 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.
About 2.4 g of CO₂ per visit
2.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.42 g of CO₂e: 290.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
38 text elements with low contrast
38 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
41 images without alt text
41 images have no alt text, which hurts accessibility and image search.
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.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (11 elements)
ARIA role should be appropriate for the element: 11 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (10 characters)
Your title is only 10 characters: “Fishermans”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (34 characters)
Your meta description is only 34 characters: “A melhor linha de pesca do Brasil.”. 70 to 160 characters is enough to sell the click.
86 internal links, 15 external
The homepage links to 86 pages on fishermans.com.br and 15 external pages.
6 checks passed
One H1 headline
Your main headline reads: “@media screen and (max-width: 749px) { .header__heading-logo--main-desktop { display: none !important; } .header__headi…”.
Canonical URL set
The canonical URL is https://fishermans.com.br/.
Structured data in place
Structured data found: Organization and WebSite.
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://fishermans.com.br/sitemap.xml.
AI search readiness
No llms.txt
There is no https://fishermans.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,137 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://fishermans.com.br/pages/kits has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://fishermans.com.br/pages/kits has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
5 checks passed
Linked pages load
4 pages of 15 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 63 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://fishermans.com.br/cdn/shop/t/2/assets/shrigma_mod_propria.css?v=4042' because its …”.
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 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 931 words of copy
The homepage carries about 931 words of visible text.
4 checks passed
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
33 other companies contacted
Loading the homepage contacts 33 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 fishermans.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
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on fishermans.com.br, including 21 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.