marketstar.com website review

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

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

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

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

8 third-party services load with your homepage (Google CDN, Usercentrics CMP and Other Google APIs/SDKs and others), adding 1.7 MB and 1.1 s of main-thread time.

Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

Google CDN costs a phone 630 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.

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

Usercentrics CMP costs a phone 323 ms of main-thread work and 188 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.

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

About 32 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.

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

7 KiB could be saved by minifying CSS.

15 KiB could be saved by minifying JavaScript.

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.

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.

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

Your largest element takes 19.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to operate our website, improve your experie…”.

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

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

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

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

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

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

Your homepage downloads 4.9 MB in 145 requests on a phone: scripts 2.0 MB (56), images 1.3 MB (45) and media 569 KiB (1). Under 2 MB keeps phones on slow connections fast.

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

1 image (46 KiB) is 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

Interactive controls must not be nested: 17 elements on the page fail this check, rated serious by axe-core.

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

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h4, h4 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.

Your title is 72 characters, so Google will cut it off around 60: “Enterprise B2B Sales Outsourcing & Partner Channel Strategy | MarketStar”.

There are 5 <h1> headlines (“Specialist-Led Sales Execution for B2B Enterprise…”, “MarketStar Recognized as a Leader in the 2025 B2B…” and “MarketStar Foundation: Driven by Purpose. Committ…”). One clear main headline is easier for people and search engines.

20 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 239 pages on marketstar.com and 8 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

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

robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

9 of 22 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 “depth2Item is not defined”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 2,117 words of visible text.

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

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