mscdirect.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 2.8 s

  2.8 s

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

• Real-user FCP: 2.8 s

  2.8 s

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

• Real-user TTFB: 1.0 s

  1.0 s

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

• Tap response (INP) got 10% slower for real visitors

  +10%

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

• Largest content (LCP) held steady for real visitors

  +5%

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

• About 0.1 g of CO₂ per visit

  0.14 g

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

• Documents must have <title> element to aid in navigation (1 element)

  Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• Frames without titles

  1 frame has no title, so screen-reader users cannot tell what it contains.

  Elements (1)

• <html> element must have a lang attribute (1 element)

  <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• 1 image without alt text

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

  View source

• No main landmark

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

  Elements (1)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• No page language

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

  View source

• Page is set to noindex

  The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  View source

• No meta description

  No meta description, so Google writes its own snippet from whatever text it finds.

• No H1 headline

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

• Title is short (13 characters)

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

  View source

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

• No social preview image

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

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

• No favicon declared

  No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

• No X (Twitter) card tag

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

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

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• Only about 75 words

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

• 7 cookies set on arrival

  7

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