boxpeg.com website review

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

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

21 KiB could be saved by minifying CSS.

1 long task block the main thread while loading, the longest for 78 ms. During a long task the page ignores taps.

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

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

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

2 third-party services load with your homepage (WordPress Site Stats and JSDelivr CDN), adding 13 KiB and 2 ms of main-thread time.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 image (31 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 0.40 g of CO₂e: 47.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

Some list items are not inside a list.

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

The page declares lang=“en_GB”, which is not a usable language code, so screen readers and translation tools guess.

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

Your meta description is only 63 characters: “Specialists in engineered, scalable APIs and SaaS applications.”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Engineering software” and “Specialists in engineered, scalable APIs and SaaS…”). One clear main headline is easier for people and search engines.

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

/about, /blog, /contact, /setting-up-a-static-web-app-with-aws, /keeping-our-ubuntu-machines-up-to-date-automatically and /how-we-use-heroku-for-continuous-integration-and-deployment have no meta description, so Google writes the search snippet from whatever text it finds.

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

/blog and /contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

5 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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

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

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 198 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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

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.