Website review, no card needed
orinter.com.br website review
Visit site (opens in a new tab)Reviewed 19 November 202642 issues · 64 checks
This review found 42 issues worth fixing on orinter.com.br, 17 of them high impact, across 64 checks. The most urgent: improve image delivery. 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.7 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.7 s |
| Aug 15, 2026 | 4.8 s |
| Aug 22, 2026 | 4.7 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.5 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.6 s |
| Oct 10, 2026 | 5.0 s |
| Oct 17, 2026 | 4.8 s |
| Oct 24, 2026 | 4.8 s |
| Oct 31, 2026 | 4.7 s |
| Nov 7, 2026 | 4.7 s |
| Nov 14, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 185 ms |
| Jun 6, 2026 | 184 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 198 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 159 ms |
| Sep 5, 2026 | 160 ms |
| Sep 12, 2026 | 153 ms |
| Sep 26, 2026 | 153 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 159 ms |
| Oct 31, 2026 | 169 ms |
| Nov 7, 2026 | 171 ms |
| Nov 14, 2026 | 169 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
4.4 s
8.7 s
13.1 s
17.5 s
21.8 s
26.2 s
30.6 s
34.9 s
Speed
Improve image delivery
4.2 s · 7.3 MB46 images could be 7.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.2 s faster on a phone.
Reduce unused JavaScript
1.6 s · 313 KiBAbout 313 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, infotravel.com.br and Cloudflare CDN and others), adding 8.6 MB and 398 ms of main-thread time.
Firebase adds 0 ms
0 msFirebase costs a phone 0 ms of main-thread work and 8.3 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.
Render-blocking requests
850 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Use efficient cache lifetimes
300 ms · 66 KiB1 file is served with short cache lifetimes, so returning visitors download them again (66 KiB).
Legacy JavaScript
300 ms · 22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 294 ms
294 msGoogle Tag Manager costs a phone 294 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.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 27 KiB27 KiB could be saved by minifying JavaScript.
Reduce unused CSS
18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page.
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.
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.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 13.3 s
13.3 sYour largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “imagem”.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.3 s
13.3 sThe page becomes fully interactive after 13.3 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.384
0.384The layout shifts by 0.384 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.24
0.24For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.
49 images without width and height
49 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 476 ms
476 msScripts block taps and scrolling for 476 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 185 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 4.8 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 168 ms
168 msReal visitors wait 168 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 444 ms
444 msReal visitors wait 444 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 9.2 MB in 93 requests
9.2 MBYour homepage downloads 9.2 MB in 93 requests on a phone: images 8.4 MB (51), scripts 658 KiB (19) and fonts 166 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 2.6 g of CO₂ per visit
2.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.61 g of CO₂e: 313.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (21 characters)
Your title is only 21 characters: “Orinter Tour & Travel”. 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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://orinter.com.br/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at orinter.com.br/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
AI search readiness
Most text only appears after JavaScript runs
1%A phone browser shows 172 words, but the HTML your server sends has only 2. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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://orinter.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Best practices
13 small tap targets
13 of 38 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 “Loading the script 'https://apis.google.com/js/api.js?onload=__iframefcb724784' violates the following Content Security…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 172 words
The homepage has only about 172 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.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
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.
8 other companies contacted
Loading the homepage contacts 8 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 orinter.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Framework
- Next.js
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on orinter.com.br, including 19 speed issues, 9 SEO issues and 6 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.