worldpoint.com website review

12 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, nxedge.io and Facebook and others), adding 5.5 MB and 1.1 s of main-thread time.

About 621 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 920 ms faster on a phone.

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

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

nxedge.io costs a phone 258 ms of main-thread work and 4.3 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.

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

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

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

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

151 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 32 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.

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

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

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

Your largest element takes 25.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nurse using SimPad Plus with Nursing Anne manikin”.

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

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

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

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

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

18 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' largest content (lcp) went from 6.3 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.9 MB in 308 requests on a phone: images 3.5 MB (57), scripts 1.8 MB (162) and stylesheets 239 KiB (26). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example CESEL-home-thanks.png at 1,920 px wide, shown at 390 px. Resized copies would save about 2.4 MB.

12 images (4.1 MB) are 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.

1 image further down the page (56 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

2 buttons have no accessible name, so screen readers announce just “button”.

Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

38 visible links have no text or label, so screen readers cannot say where they go.

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

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

Elements marked as presentational should be consistently ignored: 2 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.

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

Structured data found (Organization and WebSite) but with 2 problems, 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.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 302 pages on worldpoint.com and 1 external page.

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.

/blog, /contact, /catalogsearch/advanced, /worldpoint-products/cpr-taylor/cpr-taylor-replacement-parts and /worldpoint-products/baby-tyler/baby-tyler-replacement-parts have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /catalogsearch/advanced, whose canonical is /catalogsearch/advanced/index. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/catalogsearch/advanced, /worldpoint-products, /worldpoint-products/cpr-taylor, /worldpoint-products/cpr-taylor/cpr-taylor-manikins, /worldpoint-products/cpr-taylor/cpr-taylor-replacement-parts and /worldpoint-products/cpr-tommi and 2 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=36000717&tm=gtm002&Ver=2&mid=ad8217e6-3296-4910-8ace-1310778551b8&bo=1&sid=cbba16b0cdf811f186ff5d9bb820e49e&vid=cbba2210cdf811f19afe81b69d38d138&vids=1&msclkid=N&pi=91.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Chrome logged issues while loading the page (“Content security policy”).

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.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

worldpoint.com 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.

worldpoint.com'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.

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

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 654 words of visible text.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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 23 cookies, 2 of them by other companies (measured from a US location before any click).

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