apexlab.com website review

Not measured in this review.

• Real-user FCP: 1.9 s

  1.9 s

  Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 1.5 s

  1.5 s

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

• Tap response (INP) held steady for real visitors

  -3%

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

• Largest content (LCP) held steady for real visitors

  -1%

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

• Page weight: 4.6 MB

  4.6 MB

  Your homepage downloads 4.6 MB on a phone, 3.6 MB of it images (78%). Under 2 MB keeps phones on slow connections fast.

• 16 images in older formats

  16 images (2.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.

  Elements (5)

• 13 images below the first screen load straight away

  13 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• About 1.3 g of CO₂ per visit

  1.31 g

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

• 4 text elements with low contrast

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

  Elements (3)

• All page content should be contained by landmarks (22 elements)

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

  Elements (3)

• No main landmark

  The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  Elements (1)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

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

  Elements (1)

• 3 links without text

  3 visible links have no text or label, so screen readers cannot say where they go.

  Elements (3)

• Headings should not be empty (6 elements)

  Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Headings skip levels

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

  View sourceElements (3)

• Title is short (24 characters)

  Your title is only 24 characters: “Home - Apex Laboratories”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• Meta description is long (378 characters)

  Your meta description is 378 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• No social preview image

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

  View source

• 33 internal links, 11 external

  The homepage links to 33 pages on apexlab.com and 11 external pages.

• 3 pages without an H1

  /company-profile, /cmds-desk and /products/anti-emetics have no <h1> headline, so visitors and search engines get no clear main topic.

• 1 page with very little text

  /products/anti-emetics has 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.

• 3 pages slow to respond

  /company-profile, /cmds-desk and /products/anti-emetics took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 4 broken images

  4 images failed to load on a phone, for example https://staging.apexlab.com/wp-content/uploads/2022/01/1-3.jpg.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

• 2 insecure resources on an https page

  2 resources load over plain http on your https page (for example http://staging.apexlab.com/wp-content/uploads/2022/01/1-3.jpg); browsers block or warn about them.

• 4 broken external links

  4 links to other sites are dead, for example http://staging.apexlab.com/package/ (404).

• No HSTS header

  No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

• No Content-Security-Policy

  No Content-Security-Policy header, the main browser-side defence against injected scripts.

• No clickjacking protection

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

• No X-Content-Type-Options

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

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

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

• No CAA record

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

• DNSSEC is off

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

• No call to action on the first screen

  On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

• Thin social proof

  Social proof on the homepage: 12 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

• No analytics detected

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

• Phone number is not tap-to-call

  Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

• No form on the homepage

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

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 406 words of copy

  The homepage carries about 406 words of visible text.

• Email authentication score: 85/100

  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.

• 1 cookie set on arrival

  1

  Opening the homepage sets 1 cookie (measured from a US location before any click).

• No consent tool detected

  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.

• 4 other companies contacted

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