brunomd.com website review

• Reduce unused JavaScript

  5.0 s · 1,023 KiB

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

• Use efficient cache lifetimes

  3.6 s · 826 KiB

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

• Improve image delivery

  3.5 s · 857 KiB

  14 images could be 857 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.

  Show on pageElements (3)

• Mobile performance score: 41

  41/100

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

• 4,199 HTML elements

  The page has 4,199 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

• Main-thread work: 4.1 s

  A phone's processor spends 4.1 s on main-thread work while loading, 2.6 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 (Hotjar, Hubspot and hsappstatic.net and others), adding 2.4 MB and 1.7 s of main-thread time.

• Hotjar adds 531 ms

  531 ms

  Hotjar costs a phone 531 ms of main-thread work and 261 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.

• Hubspot adds 368 ms

  368 ms

  Hubspot costs a phone 368 ms of main-thread work and 576 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.

• hsappstatic.net adds 336 ms

  336 ms

  hsappstatic.net costs a phone 336 ms of main-thread work and 718 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

  400 ms

  4 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.

• 17 long tasks on the main thread

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

• Google Tag Manager adds 168 ms

  168 ms

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

• Yotpo adds 145 ms

  145 ms

  Yotpo costs a phone 145 ms of main-thread work and 391 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.

• Reduce unused CSS

  150 ms · 79 KiB

  About 79 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 · 47 KiB

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

• Font display

  50 ms

  Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

• Forced reflow

  Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

• Minify JavaScript

  3 KiB

  3 KiB could be saved by minifying JavaScript.

• First Contentful Paint: 12.0 s

  12.0 s

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

• Largest Contentful Paint: 23.4 s

  23.4 s

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

  Show on pageElements (1)

• Time to Interactive: 25.1 s

  25.1 s

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

• Speed Index: 12.0 s

  12.0 s

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

• Total Blocking Time: 557 ms

  557 ms

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

• 1 image without width and height

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

  Show on pageElements (1)

• Not enough real-visitor data yet

  Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

• Page weight: 14.8 MB in 155 requests

  14.8 MB

  Your homepage downloads 14.8 MB in 155 requests on a phone: media 10.8 MB (7), scripts 2.3 MB (51) and images 1.2 MB (40). Under 2 MB keeps phones on slow connections fast.

• 4 images in older formats

  4 images (168 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.

  Elements (4)

• 3 images below the first screen load straight away

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

  Elements (3)

• About 4.2 g of CO₂ per visit

  4.20 g

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

Not measured in this review.

• No page title

  Your page has no <title>, so Google has to invent the blue link in search results.

• No H1 headline

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

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

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

• Open Graph partly set

  Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  View source

• No X (Twitter) card tag

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

• Most text only appears after JavaScript runs

  0%

  A phone browser shows 486 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.

• No llms.txt

  There is no https://brunomd.com/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 third-party cookie

  1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

• 2 JavaScript errors while loading

  2 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”).

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

  The homepage carries about 486 words of visible text.

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

• 24 cookies set on arrival

  24

  Opening the homepage sets 24 cookies, 8 of them by other companies (measured from a US location before any click).

• 40 other companies contacted

  Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.