Website review, no card needed

marelli.com.br logo

marelli.com.br website review

Visit site (opens in a new tab)Reviewed 30 October 202658 issues · 96 checks

This review found 58 issues worth fixing on marelli.com.br, 24 of them high impact, across 96 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.0 s2.0 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.8 s
May 23, 20262.9 s
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.4 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.6 s
Jul 11, 20263.1 s
Jul 18, 20263.3 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.6 s
Aug 15, 20263.7 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.7 s
Sep 26, 20263.6 s
Oct 3, 20263.7 s
Oct 10, 20263.8 s
Oct 17, 20263.7 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
323 ms123 msMay 9Oct 24282 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026146 ms
May 16, 2026186 ms
May 23, 2026215 ms
May 30, 2026216 ms
Jun 6, 2026225 ms
Jun 13, 2026187 ms
Jun 20, 2026165 ms
Jun 27, 2026165 ms
Jul 4, 2026199 ms
Jul 11, 2026246 ms
Jul 18, 2026280 ms
Jul 25, 2026293 ms
Aug 1, 2026290 ms
Aug 8, 2026300 ms
Aug 15, 2026278 ms
Aug 22, 2026289 ms
Aug 29, 2026290 ms
Sep 5, 2026282 ms
Sep 12, 2026299 ms
Sep 19, 2026288 ms
Sep 26, 2026294 ms
Oct 3, 2026292 ms
Oct 10, 2026286 ms
Oct 17, 2026280 ms
Oct 24, 2026282 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

Full-page screenshot of marelli.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. marelli.com.br at 1.2 s1.2 s
  2. marelli.com.br at 2.5 s2.5 s
  3. marelli.com.br at 3.7 s3.7 s
  4. marelli.com.br at 5.0 s5.0 s
  5. marelli.com.br at 6.2 s6.2 s
  6. marelli.com.br at 7.4 s7.4 s
  7. marelli.com.br at 8.7 s8.7 s
  8. marelli.com.br at 9.9 s9.9 s

Speed

14 to fix22
  • Reduce unused JavaScript

    4.7 s · 2.1 MB

    About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

  • Use efficient cache lifetimes

    1.0 s · 761 KiB

    35 files are served with short cache lifetimes, so returning visitors download them again (761 KiB).

  • atendimen.to adds 1.3 s

    1.3 s

    atendimen.to costs a phone 1.3 s of main-thread work and 2.0 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.

  • vtexassets.com adds 1.2 s

    1.2 s

    vtexassets.com costs a phone 1.2 s of main-thread work and 3.3 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.

  • Main-thread work: 14.3 s

    A phone's processor spends 14.3 s on main-thread work while loading, 7.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google CDN adds 1.1 s

    1.1 s

    Google CDN costs a phone 1.1 s of main-thread work and 1.4 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: 22

    22/100

    Your mobile performance score is 22. 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 (atendimen.to, vtexassets.com and Google CDN and others), adding 8.9 MB and 5.9 s of main-thread time.

  • Reduce unused CSS

    880 ms · 594 KiB

    About 594 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 880 ms faster on a phone.

  • Improve image delivery

    950 ms · 315 KiB

    8 images could be 315 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

  • Google Tag Manager adds 818 ms

    818 ms

    Google Tag Manager costs a phone 818 ms of main-thread work and 543 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.

  • YouTube adds 718 ms

    718 ms

    YouTube costs a phone 718 ms of main-thread work and 1,003 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.

  • Render-blocking requests

    450 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 399 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    250 ms · 62 KiB

    Polyfills for old browsers add 62 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • 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.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 17 ms

    17 ms

    Your server sent the HTML in 17 ms, well inside Google's 600 ms guideline.

Core Web Vitals

15 to fix0
  • 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 CLS: 0.28

    0.28

    For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.

  • Real-user FCP: 3.4 s

    3.4 s

    Real visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.

  • Largest Contentful Paint: 16.7 s

    16.7 s

    Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 23.9 s

    23.9 s

    Visually, the page fills in at 23.9 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 47.3 s

    47.3 s

    The page becomes fully interactive after 47.3 s. Good is under 3.8 s.

  • First Contentful Paint: 6.7 s

    6.7 s

    The first text or image appears after 6.7 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 3.4 s

    3.4 s

    Scripts block taps and scrolling for 3.4 s in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 3.5 s

    3.5 s

    Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 335 ms

    335 ms

    Real visitors wait 335 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 69% slower for real visitors

    +69%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 146 ms to 282 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 44% slower for real visitors

    +44%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Real-user TTFB: 1.3 s

    1.3 s

    Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.119

    0.119

    The layout shifts by 0.119 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

Images and page weight

4 to fix43
  • Page weight: 9.1 MB in 198 requests

    9.1 MB

    Your homepage downloads 9.1 MB in 198 requests on a phone: scripts 4.4 MB (77), HTML 2.3 MB (8) and images 1.2 MB (33). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

    6 images further down the page (788 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images far larger than shown

    436 KiB

    3 images are downloaded at several times the size a phone draws them, for example 3ac12e79-4692-49f8-bd72-e3f2bb546f75___26f2127874677d2d6ca9f at 1,600 px wide, shown at 207 px. Resized copies would save about 436 KiB.

  • 4 images in older formats

    4 images (492 KiB) 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.

  • About 2.6 g of CO₂ per visit

    2.59 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.59 g of CO₂e: 311.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

10 to fixGoogle 7486
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 31 text elements with low contrast

    31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 14 tap targets too small

    14 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • All page content should be contained by landmarks (19 elements)

    All page content should be contained by landmarks: 19 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.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • Title is short (7 characters)

    Your title is only 7 characters: “Marelli”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (ItemList, VideoObject and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 21 internal links, 10 external

    The homepage links to 21 pages on marelli.com.br and 10 external pages.

5 checks passed
  • Meta description: 87 characters

    Your meta description is 87 characters: “Cadeiras e móveis de qualidade é na Marelli! Tudo em até 12x. Entrega para todo Brasil.”.

  • One H1 headline

    Your main headline reads: “Marelli - Uma história escrita pelo empreendedorismo e inovação.”.

  • Canonical URL set

    The canonical URL is https://www.marelli.com.br/.

  • 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.marelli.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.marelli.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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (346 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix71
  • 5 pages without a title

    https://www.marelli.com.br/2657-impact/p, https://www.marelli.com.br/6052-rit/p, https://www.marelli.com.br/1605-pro-fit/p, https://www.marelli.com.br/2557-move/p and https://www.marelli.com.br/213-you/p have no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.marelli.com.br/unique is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 12 pages share a meta description

    https://www.marelli.com.br/seja-um-lojista, https://www.marelli.com.br/blog, https://www.marelli.com.br/onde-comprar, https://www.marelli.com.br/biblioteca, https://www.marelli.com.br/contato and https://www.marelli.com.br/compre-online and 6 others use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://www.marelli.com.br/seja-um-lojista, https://www.marelli.com.br/blog, https://www.marelli.com.br/onde-comprar, https://www.marelli.com.br/biblioteca, https://www.marelli.com.br/contato and https://www.marelli.com.br/unique have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://www.marelli.com.br/blog, https://www.marelli.com.br/onde-comprar, https://www.marelli.com.br/biblioteca, https://www.marelli.com.br/contato and https://www.marelli.com.br/213-you/p have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 pages slow to respond

    https://www.marelli.com.br/compre-online and https://www.marelli.com.br/unique took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

Best practices

3 to fixGoogle 7385
  • 21 small tap targets

    21 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 394 words of copy

    The homepage carries about 394 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “DOWNLOAD DE CATÁLOGOS →”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 3 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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 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.

  • 43 other companies contacted

    Loading the homepage contacts 43 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 marelli.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
React
Analytics
Google Tag Manager
Hosting
Cyberweb Networks Ltda

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 58 issues on marelli.com.br, including 29 speed issues, 3 SEO 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25