worthpoint.com website review

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

crcldu.com costs a phone 1.3 s of main-thread work and 218 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 5.2 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

5 third-party services load with your homepage (crcldu.com, px-cloud.net and px-client.net and others), adding 595 KiB and 2.1 s of main-thread time.

Your mobile performance score is 62 (desktop: 64). Pages that score under 90 lose visitors before the first paint.

px-cloud.net costs a phone 814 ms of main-thread work and 293 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 699 ms. During a long task the page ignores taps.

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

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

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

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.

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

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Press & Hold to confirm you are a human (and not a bot).”.

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

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

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

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

All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate 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.

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

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

The page answers with an error status, so search engines may drop it.

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

No XML sitemap at https://www.worthpoint.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 114 pages on worthpoint.com and 17 external pages.

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

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

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

https://www.worthpoint.com/dictionary, https://www.worthpoint.com/live-auctions/events, https://www.worthpoint.com/live-auctions/items and https://www.worthpoint.com/data-partners all use the title “WorthPoint”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.worthpoint.com/worthopedia, https://www.worthpoint.com/marks, https://www.worthpoint.com/library, https://www.worthpoint.com/dictionary, https://www.worthpoint.com/live-auctions/events and https://www.worthpoint.com/live-auctions/items and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.worthpoint.com/articles/searchResults and https://www.worthpoint.com/page/newsletter-landing-page use the same meta description. A description written for each page earns more clicks.

https://www.worthpoint.com/worthopedia, https://www.worthpoint.com/marks, https://www.worthpoint.com/library, https://www.worthpoint.com/dictionary, https://www.worthpoint.com/data-partners and https://www.worthpoint.com/articles/searchResults have no <h1> headline, so visitors and search engines get no clear main topic.

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

7 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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

Large scripts ship without source maps.

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

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.

Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,841 words of visible text.

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

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