ascm.org website review

71 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).

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

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

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

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

8 third-party services load with your homepage (mypurecloud.com, Google Tag Manager and Google CDN and others), adding 4.0 MB and 2.3 s of main-thread time.

About 297 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

mypurecloud.com costs a phone 678 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.

The page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.

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

24 images could be 591 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

PayPal costs a phone 300 ms of main-thread work and 467 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.

Salesforce.com costs a phone 222 ms of main-thread work and 592 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.

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

The HTML itself could arrive about 250 ms sooner: redirects, a slow server response or missing compression delay everything after it.

222 KiB could be saved by minifying JavaScript.

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

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

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.

4 KiB could be saved by minifying CSS.

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 see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “With over 70 years of supply chain leadership, we transform…”.

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

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

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

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

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

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

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

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

Your homepage downloads 8.0 MB in 165 requests on a phone: scripts 5.4 MB (58), images 1.5 MB (43) and other files 499 KiB (35). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 2.27 g of CO₂e: 272.6 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 on the page fails this check, rated serious by axe-core.

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

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

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

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

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.

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://ascm.org/sitemap.xml, so Google discovers your pages only by following 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 is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

3 links have no real href, so search engines can't follow them.

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

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

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

No viewport meta tag, so phones render the desktop layout zoomed out.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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 (Forbidden)”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

No character set is declared, so some characters can render as gibberish.

Large scripts ship without source maps.

http://ascm.org does not redirect to https, so some visitors land on the insecure version.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ascm.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

ascm.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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 0 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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