Website review, no card needed
ton.com.br website review
Visit site (opens in a new tab)Reviewed 20 November 202635 issues · 81 checks
This review found 35 issues worth fixing on ton.com.br, 15 of them high impact, across 81 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.8 s |
| Oct 31, 2026 | 3.8 s |
| Nov 7, 2026 | 3.8 s |
| Nov 14, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 459 ms |
| Jun 6, 2026 | 466 ms |
| Jun 13, 2026 | 471 ms |
| Jun 20, 2026 | 479 ms |
| Jun 27, 2026 | 480 ms |
| Jul 4, 2026 | 483 ms |
| Jul 11, 2026 | 487 ms |
| Jul 18, 2026 | 479 ms |
| Jul 25, 2026 | 487 ms |
| Aug 1, 2026 | 488 ms |
| Aug 8, 2026 | 487 ms |
| Aug 15, 2026 | 494 ms |
| Aug 22, 2026 | 499 ms |
| Aug 29, 2026 | 512 ms |
| Sep 5, 2026 | 527 ms |
| Sep 12, 2026 | 534 ms |
| Sep 19, 2026 | 532 ms |
| Sep 26, 2026 | 523 ms |
| Oct 3, 2026 | 512 ms |
| Oct 10, 2026 | 506 ms |
| Oct 17, 2026 | 507 ms |
| Oct 24, 2026 | 517 ms |
| Oct 31, 2026 | 527 ms |
| Nov 7, 2026 | 539 ms |
| Nov 14, 2026 | 553 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.3 s
2.6 s
3.8 s
5.1 s
6.4 s
7.7 s
8.9 s
10.2 s
Speed
Reduce unused JavaScript
1.4 s · 236 KiBAbout 236 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.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
600 ms · 147 KiB4 files are served with short cache lifetimes, so returning visitors download them again (147 KiB).
Improve image delivery
500 ms · 34 KiB3 images could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Reduce unused CSS
300 ms · 34 KiBAbout 34 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 307 ms. During a long task the page ignores taps.
Render-blocking requests
300 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,344 HTML elements
The page has 2,344 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
200 ms · 17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (securiti.ai, stone.com.br and Amplitude Mobile Analytics), adding 429 KiB and 77 ms of main-thread time.
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: 19 ms
19 msYour server sent the HTML in 19 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 INP: 702 ms
702 msReal visitors wait 702 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.856
0.856The layout shifts by 0.856 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 7.2 s
7.2 sYour largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “black ton”.
Speed Index: 6.3 s
6.3 sVisually, the page fills in at 6.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.0 s
8.0 sThe page becomes fully interactive after 8.0 s. Good is under 3.8 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 925 ms
925 msReal visitors wait 925 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 220 ms
220 msScripts block taps and scrolling for 220 ms in total while the page loads. Good is under 200 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 459 ms to 553 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Images and page weight
About 0.3 g of CO₂ per visit
0.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.30 g of CO₂e: 36.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.1 MB in 124 requests
1.1 MBYour homepage downloads 1.1 MB in 124 requests on a phone: scripts 612 KiB (78), images 219 KiB (27) and fonts 89 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (105 elements)
All page content should be contained by landmarks: 105 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.
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.
27 links without text
27 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 57 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
85 internal links, 35 external
The homepage links to 85 pages on ton.com.br and 35 external pages.
8 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Ton tem as maquininhas com as menores taxas do Brasil, o TapTon para vender pelo celular e Super Conta digital pra faze…”.
One H1 headline
Your main headline reads: “BLACK FRIDAYDA MENOR TAXAÉ COM O TON”.
Title: 45 characters
Your title is a healthy 45 characters: “Ton - Maquininhas com taxas a partir de 0,57%”.
Canonical URL set
The canonical URL is https://www.ton.com.br/.
Structured data in place
Structured data found: FAQPage.
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://www.ton.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,062 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ton.com.br/llms.txt (3 KiB, 16 links), a plain-text guide to the site for AI tools.
Other pages
9 linked pages are broken
Your homepage links to https://www.ton.com.br/maquininhas, https://www.ton.com.br/maquininha/t1, https://www.ton.com.br/maquininha/t2, https://www.ton.com.br/tap-to-pay-no-iphone, https://www.ton.com.br/link-de-pagamento and https://www.ton.com.br/pix-na-maquininha and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.
6 checks passed
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
28 small tap targets
28 of 66 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.
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 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,488 words of copy
The homepage carries about 1,488 words of visible text.
3 checks passed
17 short forms
17 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: a star rating and 13 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Amplitude (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
6 other companies contacted
Loading the homepage contacts 6 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 ton.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
- Tailwind CSS
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Akamai
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on ton.com.br, including 19 speed issues and 3 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.