Website review, no card needed
baciodilatte.com.br website review
Visit site (opens in a new tab)Reviewed 28 October 202646 issues · 85 checks
This review found 46 issues worth fixing on baciodilatte.com.br, 19 of them high impact, across 85 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.1 s |
| May 16, 2026 | 6.3 s |
| May 23, 2026 | 6.4 s |
| May 30, 2026 | 6.5 s |
| Jun 6, 2026 | 6.3 s |
| Jun 13, 2026 | 6.3 s |
| Jun 20, 2026 | 6.5 s |
| Jun 27, 2026 | 6.7 s |
| Jul 4, 2026 | 6.7 s |
| Jul 11, 2026 | 6.8 s |
| Jul 18, 2026 | 6.7 s |
| Jul 25, 2026 | 6.5 s |
| Aug 1, 2026 | 6.5 s |
| Aug 8, 2026 | 6.5 s |
| Aug 15, 2026 | 6.5 s |
| Aug 22, 2026 | 6.5 s |
| Aug 29, 2026 | 6.4 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.1 s |
| Sep 19, 2026 | 6.0 s |
| Sep 26, 2026 | 6.2 s |
| Oct 3, 2026 | 6.1 s |
| Oct 10, 2026 | 6.1 s |
| Oct 17, 2026 | 6.1 s |
| Oct 24, 2026 | 5.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 167 ms |
| May 16, 2026 | 167 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 163 ms |
| Jun 6, 2026 | 162 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 166 ms |
| Jun 27, 2026 | 167 ms |
| Jul 4, 2026 | 168 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 168 ms |
| Jul 25, 2026 | 168 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 177 ms |
| Sep 5, 2026 | 177 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 182 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 188 ms |
| Oct 17, 2026 | 189 ms |
| Oct 24, 2026 | 187 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.7 s
1.5 s
2.2 s
2.9 s
3.7 s
4.4 s
5.1 s
5.9 s
Speed
Use efficient cache lifetimes
8.4 s · 4.1 MB111 files are served with short cache lifetimes, so returning visitors download them again (4.1 MB).
Render-blocking requests
6.1 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.1 s.
Reduce unused JavaScript
4.3 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Reduce unused CSS
2.0 s · 349 KiBAbout 349 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Insider and Facebook and others), adding 1.9 MB and 1.3 s of main-thread time.
Google Tag Manager adds 520 ms
520 msGoogle Tag Manager costs a phone 520 ms of main-thread work and 648 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
400 ms · 59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
Improve image delivery
311 KiB13 images could be 311 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Insider adds 190 ms
190 msInsider costs a phone 190 ms of main-thread work and 347 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.
Duplicated JavaScript
200 ms · 17 KiB17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 207 ms. During a long task the page ignores taps.
Minify CSS
100 ms · 29 KiB29 KiB could be saved by minifying CSS.
Document request latency
118 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 187 ms
187 msYour server sent the HTML in 187 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: 6.4 s
6.4 sReal visitors wait 6.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.3 s
5.3 sReal visitors see the first content after 5.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.0 s
3.0 sReal visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 9.8 s
9.8 sThe first text or image appears after 9.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 17.5 s
17.5 sYour largest element takes 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Gelatos CONHEÇA +”.
Speed Index: 16.4 s
16.4 sVisually, the page fills in at 16.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 34.4 s
34.4 sThe page becomes fully interactive after 34.4 s. Good is under 3.8 s.
Total Blocking Time: 450 ms
450 msScripts block taps and scrolling for 450 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.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 167 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.1 s to 5.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 187 ms
187 msReal visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.041
0.041The layout barely moves while loading (CLS 0.041, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 180 requests
5.6 MBYour homepage downloads 5.6 MB in 180 requests on a phone: scripts 3.2 MB (58), images 1.0 MB (53) and fonts 780 KiB (5). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (105 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 190.0 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
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 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 (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.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (21 characters)
Your title is only 21 characters: “Bacio di Latte | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
14 H1 headlines
There are 14 <h1> headlines (“Ganhe 15%OFF*”, “Gelatos” and “Caffetteria”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at baciodilatte.com.br/robots.txt, the first file search crawlers ask for.
53 internal links, 26 external
The homepage links to 53 pages on baciodilatte.com.br and 26 external pages.
4 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Gelatos de raízes italianas feitos artesanalmente e com ingredientes de altíssima qualidade. Acesse e conheça todos os …”.
Canonical URL set
The canonical URL is https://baciodilatte.com.br/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
XML sitemap found
Your XML sitemap is reachable at https://baciodilatte.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (1,281 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://baciodilatte.com.br/presentes and https://baciodilatte.com.br/presenteaveis all use the title “Bacio di Latte | Presentes”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://baciodilatte.com.br/picolesinsanos, https://baciodilatte.com.br/presentes, https://baciodilatte.com.br/produtos/confeitaria, https://baciodilatte.com.br/milkshakes, https://baciodilatte.com.br/giftcard and https://baciodilatte.com.br/baixe-o-app and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://baciodilatte.com.br/produtos/caffeteria, whose canonical is https://baciodilatte.com.br/produtos/caffetteria-cafes-bolos-e-doces-bacio-di-latte. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages slow to respond
https://baciodilatte.com.br/picolesinsanos, https://baciodilatte.com.br/produtos/gelato, https://baciodilatte.com.br/produtos/caffeteria, https://baciodilatte.com.br/presentes, https://baciodilatte.com.br/bacio-casa and https://baciodilatte.com.br/produtos/confeitaria and 7 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 21 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 24 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 “Cannot read properties of null (reading 'addEventListener')”.
No HTML doctype
The page has no <!DOCTYPE html>, so browsers render it in quirks mode.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
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 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 254 words of copy
The homepage carries about 254 words of visible text.
2 checks passed
4 short forms
4 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
41 other companies contacted
Loading the homepage contacts 41 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 baciodilatte.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
- CMS
- WordPress
- Framework
- React
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- GoDaddy
Company
- Founded
- 2011
- Headquarters
- São Paulo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on baciodilatte.com.br, including 22 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.