pesi.com website review

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

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

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

moonshot-ai.com costs a phone 1.5 s of main-thread work and 73 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (moonshot-ai.com, Google/Doubleclick Ads and Hubspot and others), adding 1.7 MB and 3.1 s of main-thread time.

Google/Doubleclick Ads costs a phone 497 ms of main-thread work and 724 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.

Hubspot costs a phone 368 ms of main-thread work and 507 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 HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

osano.com costs a phone 350 ms of main-thread work and 96 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 232 ms. During a long task the page ignores taps.

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

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

About 45 KiB of CSS is downloaded but never applied on this page.

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

3 KiB could be saved by minifying CSS.

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

Your largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pesi Save25 Fall 300X250”.

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

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

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

The layout shifts by 0.103 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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-24, real Chrome visitors' tap response (inp) went from 163 ms to 176 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 4.4 MB in 172 requests on a phone: scripts 2.0 MB (64), fonts 1.3 MB (17) and HTML 592 KiB (7). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 148.4 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.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

58 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

Your title is 79 characters, so Google will cut it off around 60: “Continuing Education for Mental Health, Rehab & Healthcare Professionals | PESI”.

Your meta description is 247 characters; Google truncates after about 160, so the end of your pitch is cut.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 572 pages on pesi.com and 20 external pages.

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

Your homepage links to https://www.pesi.com/find, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.pesi.com/shoppingcart is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.pesi.com/healthcare, https://www.pesi.com/rehab, https://www.pesi.com/summits-conferences and https://www.pesi.com/contact-us/group-training have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://content.verasafe.com/trust-seal/badge/badge.css' from origin 'https://www.pesi.com…”.

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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.

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 3,041 words of visible text.

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

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

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