speedlify2

Stack

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-30 → 2026-08-26).

Scores

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 12.74 s.

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

40.4% of pixels differ — parts of the page change. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

LCP Subparts lab observed, unthrottled

The subparts attribute LCP to your server, resource discovery, download, or rendering. Note that the Lab metrics LCP metric shown above is throttled.

Field data Chrome UX Report, origin-level

Real Chrome users, 28-day trailing window (2026-07-30 → 2026-08-26).

Lab LCP vs Field LCP

The lab LCP is 4.39× the field p75 — real users likely have above-average hardware or network connectivity.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Page weight

By resource type

• script 81.9% 6.75 MB · 133 req
• other 5.8% 477 kB · 97 req
• font 5.3% 436 kB · 7 req
• stylesheet 4% 327 kB · 8 req
• image 2.5% 207 kB · 25 req
• document 0.5% 43.7 kB · 4 req

Third parties 28 entities

4.69 MB transferred, 1.98 s on the main thread.

Page health

Main thread work

Axe violations axe-core 4.13.0, full rule set

96 violating nodes across 11 rules, 1640 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

• moderate region — All page content should be contained by landmarks 75 nodes
• serious svg-img-alt — <svg> elements with an img or image role must have alternative text 8 nodes
• critical aria-required-parent — Certain ARIA roles must be contained by particular parents 3 nodes
• moderate heading-order — Heading levels should only increase by one 2 nodes
• serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 2 nodes
• serious aria-command-name — ARIA commands must have an accessible name 1 node
• critical aria-required-children — Certain ARIA roles must contain particular children 1 node
• moderate landmark-banner-is-top-level — Banner landmark should not be contained in another landmark 1 node
• moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
• moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 9 of 31 audits

• svg-img-alt — SVG elements with an `img` role do not have an accessible text alternative 8 nodes
• aria-required-parent — `[role]`s are not contained by their required parent element 3 nodes
• heading-order — Heading elements are not in a sequentially-descending order 2 nodes
• list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 2 nodes
• aria-command-name — `button`, `link`, and `menuitem` elements do not have accessible names. 1 node
• aria-required-children — Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children. 1 node
• link-in-text-block — Links rely on color to be distinguishable. 1 node
• target-size — Touch targets do not have sufficient size or spacing. 1 node
• landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

Measurement log

Every stored run for this URL, newest first.

Embed this score

Use this web component to show ibm.com's scores on any website, updated whenever this instance re-measures. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.ibm.com/"></speedlify2-score>