ckr.com website review

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

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

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

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

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

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

67 KiB could be saved by minifying CSS.

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

7 third-party services load with your homepage (Optanon, Cloudflare CDN and plyr.io and others), adding 545 KiB and 183 ms of main-thread time.

38 KiB could be saved by minifying JavaScript.

13 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

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

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 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Corporate headquarters”.

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

5 images have no width and height attributes, so the layout jumps as each one loads.

carouselburger-3.png weighs 1.0 MB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example carouselburger-3.png at 1,440 px wide, shown at 355 px. Resized copies would save about 569 KiB.

Your homepage downloads 2.6 MB in 51 requests on a phone: images 1.4 MB (12), scripts 520 KiB (11) and fonts 329 KiB (4). Under 2 MB keeps phones on slow connections fast.

3 images (1.3 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 (29 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 0.73 g of CO₂e: 87.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 3 characters: “CKR”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

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

The homepage links to 12 pages on ckr.com and 4 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.

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.

/, /contact-us, /privacy-policy, /accessibility, /sms-text-program and /animal-welfare and 1 other all use the title “CKR”. Search engines can't tell which page to show for a search, so each competes with the others.

/contact-us, /privacy-policy, /accessibility, /sms-text-program, /animal-welfare and /terms-and-conditions have no meta description, so Google writes the search snippet from whatever text it finds.

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

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.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

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

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.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 166 words of visible text; thin pages give Google and first-time buyers little to go on.

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

There is no form on the homepage, so every lead has to click through to another page first.

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.

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.

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

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