marshallboya.com website review

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

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

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

About 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Optanon and others), adding 2.0 MB and 972 ms of main-thread time.

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

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

Google CDN costs a phone 338 ms of main-thread work and 1.1 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.

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

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

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

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

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

3 KiB could be saved by minifying JavaScript.

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 visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mellow Flow™ açık mavi duvarları ve Slow Swing™ koyu mavi d…”.

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

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

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

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

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

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

Your homepage downloads 3.7 MB in 46 requests on a phone: scripts 2.8 MB (18), other files 381 KiB (9) and stylesheets 218 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example dulux-cf27-colour-of-the-year-hero-global-hero.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 58 KiB.

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

6 images have no alt text, which hurts accessibility and image search.

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 67 characters, so Google will cut it off around 60: “Home Page | İç Mekan ve Dış Cephe Boyaları - Dekorasyon Fikirleri |”.

Your meta description is only 67 characters: “Home Page | İç Mekan ve Dış Cephe Boyaları - Dekorasyon Fikirleri |”. 70 to 160 characters is enough to sell the click.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.marshallboya.com/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 60 pages on marshallboya.com and 11 external pages.

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

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

Large scripts ship without source maps.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your longest form asks for 15 fields (0 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 202 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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