madebysix.com website review

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

5 third-party services load with your homepage (Google Tag Manager, prismic.io and imgix and others), adding 22.2 MB and 256 ms of main-thread time.

Vimeo costs a phone 0 ms of main-thread work and 21.2 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.

Your mobile performance score is 57 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

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

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

imgix costs a phone 0 ms of main-thread work and 709 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

Desktop scores 99 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Six is an international creative agency working at the conv…”.

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

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

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

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

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

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

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

Your homepage downloads 27.4 MB in 63 requests on a phone: media 25.9 MB (4), images 709 KiB (8) and scripts 680 KiB (24). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (46 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to 12 pages on madebysix.com and 2 external pages.

A phone browser shows 254 words, but the HTML your server sends has only 19. 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.

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.

There is no https://www.madebysix.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.

https://www.madebysix.com/projects, https://www.madebysix.com/info and https://www.madebysix.com/notes use the same meta description. A description written for each page earns more clicks.

https://www.madebysix.com/projects, https://www.madebysix.com/info, https://www.madebysix.com/notes, https://www.madebysix.com/feed and https://www.madebysix.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.madebysix.com/projects, https://www.madebysix.com/info, https://www.madebysix.com/notes, https://www.madebysix.com/feed and https://www.madebysix.com/contact 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.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 254 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and 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.

Opening the homepage sets 2 cookies (measured from a US location before any click).

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.

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