candidesk.com website review

Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, hsappstatic.net and Hubspot and others), adding 1.5 MB and 817 ms of main-thread time.

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

About 417 KiB of JavaScript is downloaded but never used on this page.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

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

6547aa392efa4dbb07d56118_logo-opensourcing.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

The homepage links to 47 pages on candidesk.com and 6 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.

We fetched 15 pages linked from your homepage (of 27 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=211061927&Ver=2&mid=e8255af9-be0f-4b70-a776-0c4c43369670&bo=1&sid=57fe9b50dbf811f1a88f75aa35ea2b75&vid=57fedd70dbf811f1a9f677e4caab36ee&vids=1&msclkid=N&pi=918639831&l.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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

Opening https://candidesk.com goes through 2 redirects before the homepage loads.

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.

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

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

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.

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

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

candidesk.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, HubSpot and Microsoft Ads (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 18 cookies, 9 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.