arkadium.com website review

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.6 MB and 1.3 s of main-thread time.

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

36 images could be 915 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Google CDN costs a phone 330 ms of main-thread work and 733 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 274 ms. During a long task the page ignores taps.

cloudfront.net costs a phone 46 ms of main-thread work and 297 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.

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

Desktop scores 60 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Only on Arkadium”.

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

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

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

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

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

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

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

Your homepage downloads 8.4 MB in 350 requests on a phone: images 3.6 MB (125), scripts 3.4 MB (77) and other files 1.1 MB (72). Under 2 MB keeps phones on slow connections fast.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious 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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

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

Structured data found (Organization and WebSite) but with 8 problems, for example “Organization: image is not an absolute URL ("<https://www.arkadium.com/#logo>")”.

The homepage links to 83 pages on arkadium.com and 9 external pages.

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

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

3 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

Large scripts ship without source maps.

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

arkadium.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 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 17 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 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.

DMARC is set to p=none, so mail pretending to be arkadium.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 5 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.