axjo.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Hubspot, lfeeder.com and hubspotusercontent-eu1.net and others), adding 433 KiB and 148 ms of main-thread time.

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

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

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 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bins, Trays & Frames”.

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

Real visitors wait 889 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Visually, the page fills in at 4.6 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.

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

Your homepage downloads 14.4 MB in 87 requests on a phone: media 7.1 MB (1), images 6.6 MB (30) and fonts 413 KiB (9). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.

5 images (2.2 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.

Hubspot_Template_800x407px-2 (kopia).png 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).

1 image further down the page (442 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 4.09 g of CO₂e: 490.5 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.

1 tap target is too small or too close together to hit reliably with a finger.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 4 elements on the page fail this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 185 pages on axjo.com and 16 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.

/products-and-services/wire-cable/filament-spools has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

axjo.com is registered until Nov 2026. Make sure auto-renew is on and the card on file is current.

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

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

Social proof on the homepage: 4 trust badges. 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.

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

DMARC is set to p=none, so mail pretending to be axjo.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.

Before a visitor clicks anything, the page loads HubSpot (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 3 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.