Website review, no card needed
focoradical.com.br website review
Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 78 checks
This review found 44 issues worth fixing on focoradical.com.br, 17 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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
57FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.6 s |
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 148 ms |
| May 2, 2026 | 150 ms |
| May 9, 2026 | 151 ms |
| May 16, 2026 | 154 ms |
| May 23, 2026 | 160 ms |
| May 30, 2026 | 168 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 206 ms |
| Jun 20, 2026 | 241 ms |
| Jun 27, 2026 | 299 ms |
| Jul 4, 2026 | 327 ms |
| Jul 11, 2026 | 338 ms |
| Jul 18, 2026 | 345 ms |
| Jul 25, 2026 | 358 ms |
| Aug 1, 2026 | 370 ms |
| Aug 8, 2026 | 378 ms |
| Aug 15, 2026 | 391 ms |
| Aug 22, 2026 | 402 ms |
| Aug 29, 2026 | 412 ms |
| Sep 5, 2026 | 423 ms |
| Sep 12, 2026 | 427 ms |
| Sep 19, 2026 | 430 ms |
| Sep 26, 2026 | 428 ms |
| Oct 3, 2026 | 423 ms |
| Oct 10, 2026 | 417 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.0 s
2.0 s
3.0 s
4.0 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Use efficient cache lifetimes
10.6 s · 13.4 MB222 files are served with short cache lifetimes, so returning visitors download them again (13.4 MB).
Render-blocking requests
2.0 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 719 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: 10.7 s
A phone's processor spends 10.7 s on main-thread work while loading, 7.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 28
28/100Your mobile performance score is 28 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,775 HTML elements
The page has 3,775 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, Facebook and ContentSquare and others), adding 1.5 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
600 ms · 600 KiBAbout 600 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 919 ms. During a long task the page ignores taps.
Improve image delivery
150 ms · 715 KiB31 images could be 715 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.
Facebook adds 558 ms
558 msFacebook costs a phone 558 ms of main-thread work and 280 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.
Legacy JavaScript
350 ms · 81 KiBPolyfills for old browsers add 81 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
ContentSquare adds 266 ms
266 msContentSquare costs a phone 266 ms of main-thread work and 160 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
102 KiBAbout 102 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 35 ms
35 msYour server sent the HTML in 35 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: 4.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 25.4 s
25.4 sThe page becomes fully interactive after 25.4 s. Good is under 3.8 s.
Total Blocking Time: 4.2 s
4.2 sScripts block taps and scrolling for 4.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 12.2 s
12.2 sVisually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Real-user INP: 478 ms
478 msReal visitors wait 478 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Tap response (INP) got 182% slower for real visitors
+182%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 148 ms to 417 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 114% slower for real visitors
+114%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.6 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 992 ms
992 msReal visitors wait 992 ms for your server to start answering (75th percentile). Good is under 800 ms.
2 checks passed
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.07
0.07The layout barely moves while loading (CLS 0.07, good is under 0.1).
Images and page weight
Page weight: 14.7 MB in 273 requests
14.7 MBYour homepage downloads 14.7 MB in 273 requests on a phone: images 6.8 MB (167), media 4.7 MB (2) and scripts 1.8 MB (46). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (543 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.
5 images far larger than shown
100 KiB5 images are downloaded at several times the size a phone draws them, for example 20261002124314255342-OKTOBERFEST-RUN-2026.png at 250 px wide, shown at 74 px. Resized copies would save about 100 KiB.
About 4.2 g of CO₂ per visit
4.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.16 g of CO₂e: 499.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (12 characters)
Your title is only 12 characters: “Foco Radical”. Between 30 and 65 characters leaves room to say what you do and for whom.
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, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.focoradical.com.br/sitemap.xml, so Google discovers your pages only by following links.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
33 internal links, 28 external
The homepage links to 33 pages on focoradical.com.br and 28 external pages.
2 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Encontre suas fotos e vídeos de corridas, ciclismo, triathlon e outros esportes. Busca por rosto, número ou nome. Mais …”.
robots.txt in place
robots.txt is in place.
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.focoradical.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 (510 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share a meta description
https://www.focoradical.com.br/site/empresa, https://www.focoradical.com.br/conteudo/fotografos, https://www.focoradical.com.br/cadastro-parceria/influencer, https://www.focoradical.com.br/cadastro-parceria/assessor and https://www.focoradical.com.br/site/faq use the same meta description. A description written for each page earns more clicks.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
7 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 6 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 6 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 “Failed to load resource: net::ERR_FAILED”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
2 checks passed
Tap targets are thumb-sized
20 of 23 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 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.
Only about 226 words
The homepage has only about 226 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Shop Foco”.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
19 other companies contacted
Loading the homepage contacts 19 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 focoradical.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
- Next.js
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on focoradical.com.br, including 25 speed issues, 7 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.