candidpro.com website review

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

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

About 189 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Accessibe Accessibility Overlay and others), adding 10.1 MB and 1.1 s of main-thread time.

website-files.com costs a phone 100 ms of main-thread work and 8.8 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 550 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.

12 images could be 469 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

Your largest element takes 17.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Clear Aligners”.

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

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

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

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

12 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 71 ms to 74 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.2 MB in 122 requests on a phone: media 7.3 MB (8), scripts 1.5 MB (43) and images 790 KiB (38). Under 2 MB keeps phones on slow connections fast.

1 image (82 KiB) is 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.

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

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

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

All page content should be contained by landmarks: 23 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.

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

There are 8 <h1> headlines (“It’s time for a healthier, more confident you”, “75%” and “Your best self.Your best health.”). One clear main headline is easier for people and search engines.

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

Structured data found (WebPage) but with 1 problem, for example “WebPage: url is not an absolute URL ("/")”.

The homepage links to 22 pages on candidpro.com and 15 external pages.

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.

/legal/privacy-statement-california has no meta description, so Google writes the search snippet from whatever text it finds.

/faq has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

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

1 link from your homepage to your own site is broken, for example https://www.candidpro.com/cdn-cgi/l/email-protection (404).

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.

HSTS is set, but max-age is 120 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://www.candidco.com/providers/home.

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.

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

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

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

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.

The homepage carries about 520 words of visible text.

candidpro.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

candidpro.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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, Hotjar and Meta Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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.

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