Website review, no card needed
leiturinha.com.br website review
Visit site (opens in a new tab)Reviewed 23 October 202654 issues · 90 checks
This review found 54 issues worth fixing on leiturinha.com.br, 18 of them high impact, across 90 checks. The most urgent: youTube adds 1.2 s. 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.8 s |
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 261 ms |
| May 9, 2026 | 264 ms |
| May 16, 2026 | 268 ms |
| May 23, 2026 | 277 ms |
| May 30, 2026 | 269 ms |
| Jun 6, 2026 | 257 ms |
| Jun 13, 2026 | 259 ms |
| Jun 20, 2026 | 262 ms |
| Jun 27, 2026 | 263 ms |
| Jul 4, 2026 | 272 ms |
| Jul 11, 2026 | 273 ms |
| Jul 18, 2026 | 273 ms |
| Jul 25, 2026 | 276 ms |
| Aug 1, 2026 | 277 ms |
| Aug 8, 2026 | 288 ms |
| Aug 15, 2026 | 299 ms |
| Aug 22, 2026 | 310 ms |
| Aug 29, 2026 | 316 ms |
| Sep 5, 2026 | 314 ms |
| Sep 12, 2026 | 308 ms |
| Sep 19, 2026 | 303 ms |
| Sep 26, 2026 | 304 ms |
| Oct 3, 2026 | 304 ms |
| Oct 10, 2026 | 316 ms |
| Oct 17, 2026 | 338 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.1 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
YouTube adds 1.2 s
1.2 sYouTube costs a phone 1.2 s of main-thread work and 1.9 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.
Mobile performance score: 18
18/100Your mobile performance score is 18 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 3.1 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 (YouTube, Google Tag Manager and Facebook and others), adding 3.1 MB and 2.3 s of main-thread time.
Reduce unused JavaScript
600 ms · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
350 ms · 1.7 MB22 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 350 ms faster on a phone.
Render-blocking requests
900 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Google Tag Manager adds 680 ms
680 msGoogle Tag Manager costs a phone 680 ms of main-thread work and 727 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
200 ms · 350 KiB8 files are served with short cache lifetimes, so returning visitors download them again (350 KiB).
Reduce unused CSS
300 ms · 123 KiBAbout 123 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.
Facebook adds 353 ms
353 msFacebook costs a phone 353 ms of main-thread work and 337 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 372 ms. During a long task the page ignores taps.
Legacy JavaScript
250 ms · 50 KiBPolyfills for old browsers add 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 68 but mobile only 18. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 4 ms
4 msYour server sent the HTML in 4 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.
Time to Interactive: 30.3 s
30.3 sThe page becomes fully interactive after 30.3 s. Good is under 3.8 s.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Semana da Criança: frete grátis e presente no primeiro kit …”.
Cumulative Layout Shift: 0.577
0.577The layout shifts by 0.577 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 351 ms
351 msReal visitors wait 351 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 261 ms to 338 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 958 ms
958 msReal visitors wait 958 ms for your server to start answering (75th percentile). Good is under 800 ms.
52 images without width and height
52 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 5.9 MB in 127 requests
5.9 MBYour homepage downloads 5.9 MB in 127 requests on a phone: scripts 3.2 MB (55), images 2.2 MB (30) and fonts 293 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
2025/Maio/receive/FINAIS_LP_Livros-InfantiS.png weighs 687 KiB. On a phone connection a single image that size takes seconds.
12 images in older formats
12 images (1.9 MB) 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.
4 images far larger than shown
408 KiB4 images are downloaded at several times the size a phone draws them, for example builder_io_assets/1706b2ab786cc9947a628ed0e9118f732bcc8fbb.g at 1,389 px wide, shown at 96 px. Resized copies would save about 408 KiB.
6 images below the first screen load straight away
6 images further down the page (591 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.69 g of CO₂e: 202.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
42 text elements with low contrast
42 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a valid value for the lang attribute (1 element)
<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (52 elements)
All page content should be contained by landmarks: 52 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Page language is “pt_BR”
The page declares lang=“pt_BR”, which is not a usable language code, so screen readers and translation tools guess.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 58 images in the HTML carry an alt attribute.
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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 favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
10 internal links, 31 external
The homepage links to 10 pages on leiturinha.com.br and 31 external pages.
5 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “O maior clube do livro infantil seleciona os melhores livros infantis todo mês para seu pequeno leitor. Faça parte do C…”.
Title: 55 characters
Your title is a healthy 55 characters: “Leiturinha | O maior clube de livros infantis do Brasil”.
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://leiturinha.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.
Some text only appears after JavaScript runs
47%The HTML your server sends has 295 of the 624 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://leiturinha.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
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.
Other pages
1 page without a title
https://leiturinha.com.br/relatorio-equidade-genero has no <title>, so Google invents the link text in results.
2 pages without a meta description
https://leiturinha.com.br/blog/o-que-vem-no-kit-leiturinha and https://leiturinha.com.br/relatorio-equidade-genero have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://leiturinha.com.br/sobre, https://leiturinha.com.br/termos/clube, https://leiturinha.com.br/politicas/privacidade, https://leiturinha.com.br/info/privacidade, https://leiturinha.com.br/info/contrato_livros_infantis and https://leiturinha.com.br/politicas/seguranca/leiturinha and 1 other use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://leiturinha.com.br/termos/clube and https://leiturinha.com.br/relatorio-equidade-genero have no <h1> headline, so visitors and search engines get no clear main topic.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
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.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
19 distorted images
19 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”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
16 of 19 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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 624 words of copy
The homepage carries about 624 words of visible text.
1 checks passed
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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.
2 cookies set on arrival
2Opening the homepage sets 2 cookies, 1 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.
16 other companies contacted
Loading the homepage contacts 16 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 leiturinha.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
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on leiturinha.com.br, including 25 speed issues, 4 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.