Website review, no card needed
margirius.com.br website review
Visit site (opens in a new tab)Reviewed 1 November 202641 issues · 72 checks
This review found 41 issues worth fixing on margirius.com.br, 13 of them high impact, across 72 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.4 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.6 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.6 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.9 s |
| Sep 19, 2026 | 5.0 s |
| Sep 26, 2026 | 5.3 s |
| Oct 3, 2026 | 5.7 s |
| Oct 10, 2026 | 5.7 s |
| Oct 17, 2026 | 5.8 s |
| Oct 24, 2026 | 5.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 141 ms |
| May 16, 2026 | 145 ms |
| May 23, 2026 | 153 ms |
| May 30, 2026 | 158 ms |
| Jun 6, 2026 | 157 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 148 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 150 ms |
| Aug 8, 2026 | 152 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 156 ms |
| Sep 19, 2026 | 161 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 218 ms |
| Oct 17, 2026 | 222 ms |
| Oct 24, 2026 | 216 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.9 s · 461 KiBAbout 461 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 691 KiB44 files are served with short cache lifetimes, so returning visitors download them again (691 KiB).
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Other Google APIs/SDKs and others), adding 831 KiB and 681 ms of main-thread time.
Improve image delivery
400 ms · 186 KiB7 images could be 186 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Render-blocking requests
500 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.
Google Tag Manager adds 418 ms
418 msGoogle Tag Manager costs a phone 418 ms of main-thread work and 486 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 265 ms. During a long task the page ignores taps.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 835 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 53 KiBAbout 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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: 5.9 s
5.9 sReal visitors wait 5.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.6 s
13.6 sYour largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner principal”.
Time to Interactive: 13.6 s
13.6 sThe page becomes fully interactive after 13.6 s. Good is under 3.8 s.
Real-user INP: 251 ms
251 msReal visitors wait 251 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 53% slower for real visitors
+53%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 141 ms to 216 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 90% slower for real visitors
+90%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.9 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 530 ms
530 msScripts block taps and scrolling for 530 ms in total while the page loads. Good is under 200 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
3 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.02
0.02The layout barely moves while loading (CLS 0.02, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 81 requests
2.1 MBYour homepage downloads 2.1 MB in 81 requests on a phone: scripts 983 KiB (10), images 843 KiB (43) and fonts 216 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (38 KiB) is 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.
About 0.6 g of CO₂ per visit
0.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.59 g of CO₂e: 71.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
46 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: 46 passed and 4 failed. 2 mores 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.
Title is short (9 characters)
Your title is only 9 characters: “MarGirius”. 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.
Meta description is short (37 characters)
Your meta description is only 37 characters: “MarGirius. Mais que Elétrica, Humana.”. 70 to 160 characters is enough to sell the click.
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.
4 checks passed
Canonical URL set
The canonical URL is https://www.margirius.com.br/.
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.margirius.com.br/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 393 words, but the HTML your server sends has only 0. 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.
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.
llms.txt published
The site publishes https://www.margirius.com.br/llms.txt (4 KiB, 0 links), a plain-text guide to the site for AI tools.
Best practices
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Blocked by cross-origin policy”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
43 of 48 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 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 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 393 words of copy
The homepage carries about 393 words of visible text.
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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
14 other companies contacted
Loading the homepage contacts 14 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 margirius.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
- Hosting
- Sucuri
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on margirius.com.br, including 21 speed issues, 5 SEO issues and 5 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.