Website review, no card needed

milium.com.br logo

milium.com.br website review

Visit site (opens in a new tab)Reviewed 31 October 202647 issues · 89 checks

This review found 47 issues worth fixing on milium.com.br, 24 of them high impact, across 89 checks. The most urgent: improve image delivery. 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
5.5 s4.3 sMay 9Oct 245.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.8 s
May 16, 20264.7 s
May 23, 20264.7 s
May 30, 20264.6 s
Jun 6, 20264.6 s
Jun 13, 20264.6 s
Jun 20, 20264.6 s
Jun 27, 20264.5 s
Jul 4, 20264.5 s
Jul 11, 20264.4 s
Jul 18, 20264.4 s
Jul 25, 20264.5 s
Aug 1, 20264.5 s
Aug 8, 20264.6 s
Aug 15, 20264.6 s
Aug 22, 20264.6 s
Aug 29, 20264.7 s
Sep 5, 20264.7 s
Sep 12, 20264.7 s
Sep 19, 20264.7 s
Sep 26, 20264.8 s
Oct 3, 20264.9 s
Oct 10, 20265.0 s
Oct 17, 20265.2 s
Oct 24, 20265.4 s
Real-visitor tap response (INP)75th percentile, phones
721 ms566 msMay 9Oct 24584 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026664 ms
May 16, 2026660 ms
May 23, 2026657 ms
May 30, 2026658 ms
Jun 6, 2026653 ms
Jun 13, 2026658 ms
Jun 20, 2026664 ms
Jun 27, 2026654 ms
Jul 4, 2026660 ms
Jul 11, 2026662 ms
Jul 18, 2026663 ms
Jul 25, 2026681 ms
Aug 1, 2026681 ms
Aug 8, 2026679 ms
Aug 15, 2026676 ms
Aug 22, 2026660 ms
Aug 29, 2026656 ms
Sep 5, 2026648 ms
Sep 12, 2026642 ms
Sep 19, 2026642 ms
Sep 26, 2026649 ms
Oct 3, 2026674 ms
Oct 10, 2026703 ms
Oct 17, 2026667 ms
Oct 24, 2026584 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 milium.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. milium.com.br at 0.9 s0.9 s
  2. milium.com.br at 1.9 s1.9 s
  3. milium.com.br at 2.8 s2.8 s
  4. milium.com.br at 3.8 s3.8 s
  5. milium.com.br at 4.7 s4.7 s
  6. milium.com.br at 5.7 s5.7 s
  7. milium.com.br at 6.6 s6.6 s
  8. milium.com.br at 7.5 s7.5 s

Speed

11 to fix44
  • Improve image delivery

    4.1 s · 1.7 MB

    7 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.1 s faster on a phone.

  • Use efficient cache lifetimes

    2.3 s · 651 KiB

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

  • Reduce unused JavaScript

    1.9 s · 716 KiB

    About 716 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Render-blocking requests

    1.1 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Facebook and others), adding 4.4 MB and 2.2 s of main-thread time.

  • vtexassets.com adds 824 ms

    824 ms

    vtexassets.com costs a phone 824 ms of main-thread work and 2.9 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.

  • Reduce unused CSS

    600 ms · 150 KiB

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

  • Google Tag Manager adds 459 ms

    459 ms

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

  • 18 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 122 KiB

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

  • 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

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 35 ms

    35 ms

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

Core Web Vitals

12 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 INP: 520 ms

    520 ms

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

  • Largest Contentful Paint: 17.9 s

    17.9 s

    Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “natal com até 50% off”.

  • Time to Interactive: 21.3 s

    21.3 s

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

  • Total Blocking Time: 893 ms

    893 ms

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user CLS: 0.21

    0.21

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

  • Real-user FCP: 2.7 s

    2.7 s

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

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 17 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

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

    +10%

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

1 checks passed
  • Cumulative Layout Shift: 0.047

    0.047

    The layout barely moves while loading (CLS 0.047, good is under 0.1).

Images and page weight

3 to fix47
  • Page weight: 4.6 MB in 163 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 163 requests on a phone: scripts 2.4 MB (63), images 1.9 MB (47) and HTML 169 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    5e598af1-09ff-41b8-ad9c-fd2699927233___c2a6445b9b6e60e95a08f is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.3 g of CO₂ per visit

    1.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.31 g of CO₂e: 157.3 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

9 to fixGoogle 6885
  • 3 buttons without a name

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

  • 9 tap targets too small

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

  • 7 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 5 links without text

    5 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).

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

4 to fixGoogle 8581
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 28 links crawlers can't follow

    28 links have no real href, so search engines can't follow them.

  • Structured data has 5 problems

    Structured data found ((untyped) and WebSite) but with 5 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

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

  • 48 internal links, 8 external

    The homepage links to 48 pages on milium.com.br and 8 external pages.

5 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Na Milium você encontra de tudo para casa, construção, papelaria e utilidades, com variedade, marcas confiáveis e soluç…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Milium | Loja Completa para Casa, Construção e Utilidades!”.

  • Canonical URL set

    The canonical URL is https://www.milium.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.milium.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.milium.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 (212 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 2 pages slow to respond

    https://www.milium.com.br/eletro and https://www.milium.com.br/ferragens took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 15 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 15 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 19 small tap targets

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

  • 5 JavaScript errors while loading

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

  • 3 low-resolution images

    3 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

4 to fix42
  • 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.

  • Only about 238 words

    The homepage has only about 238 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.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 27 cookies set on arrival

    27

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 milium.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
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on milium.com.br, including 23 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

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