https://mclarengroup.com/
65
Performance
91
Accessibility
Best Practices
100
SEO
85
Performance
91
Accessibility
92
Best pratices
100
SEO
85 FCP+10LCP+24TBT+3CLS+25SI+2 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
760 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.012
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
3.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
Diagnostics
Minimize main-thread work 9.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Other
5,393 ms
Script Evaluation
3,365 ms
Garbage Collection
173 ms
Style & Layout
124 ms
Rendering
41 ms
Script Parsing & Compilation
18 ms
Parse HTML & CSS
17 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 550 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
cdn-cookieyes.com
79 KiB
549 ms
…673e509…/script.js
(cdn-cookieyes.com)
34 KiB
549 ms
…673e509…/banner.js
(cdn-cookieyes.com)
33 KiB
0 ms
…config/CGXWeiKU.json
(cdn-cookieyes.com)
6 KiB
0 ms
Other resources
5 KiB
0 ms
prismic.io
2,424 KiB
0 ms
/mclaren/6d9adf97-….mp4
(mclaren.cdn.prismic.io)
1,295 KiB
0 ms
/mclaren/ab9cf001-…+This+is+us_Company+Brochure-1.png?auto=…
(images.prismic.io)
372 KiB
0 ms
/api/v2
(mclaren.cdn.prismic.io)
228 KiB
0 ms
…documents/search?q=…
(mclaren.cdn.prismic.io)
145 KiB
0 ms
Other resources
383 KiB
0 ms
Google Tag Manager
tag-manager
76 KiB
0 ms
/gtag/js?id=GTM-PHHFVZ5
(www.googletagmanager.com)
76 KiB
0 ms
vercel-insights.com
0 KiB
0 ms
cookieyes.com
0 KiB
0 ms
Reduce JavaScript execution time 3.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
Unattributable
5,436 ms
468 ms
0 ms
Unattributable
5,436 ms
468 ms
0 ms
mclarengroup.com
1st party
2,666 ms
2,107 ms
5 ms
…chunks/framework-5f4595e5518b5600.js
(mclarengroup.com)
1,755 ms
1,639 ms
1 ms
…chunks/main-9e4147ff57178ce2.js
(mclarengroup.com)
484 ms
326 ms
1 ms
https://mclarengroup.com
278 ms
11 ms
0 ms
…chunks/560-f3ab180386a2692e.js
(mclarengroup.com)
87 ms
69 ms
2 ms
…pages/index-632dde927b1629c9.js
(mclarengroup.com)
63 ms
62 ms
0 ms
cdn-cookieyes.com
938 ms
733 ms
1 ms
…673e509…/script.js
(cdn-cookieyes.com)
938 ms
733 ms
1 ms
Reduce unused JavaScript Potential savings of 81 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCP
Next.jsUse Webpack Bundle Analyzer to detect unused JavaScript code. Learn more
ReactIf you are not server-side rendering, split your JavaScript bundles with React.lazy(). Otherwise, code-split using a third-party library such as loadable-components.
URL
Transfer Size
Potential Savings
mclarengroup.com
1st party
104.0 KiB
47.6 KiB
…chunks/560-f3ab180386a2692e.js
(mclarengroup.com)
52.3 KiB
24.2 KiB
…chunks/541-a715c1ca5785aebf.js
(mclarengroup.com)
51.7 KiB
23.4 KiB
Google Tag Manager
tag-manager
75.8 KiB
33.4 KiB
/gtag/js?id=GTM-PHHFVZ5
(www.googletagmanager.com)
75.8 KiB
33.4 KiB
Properly size images Potential savings of 1,192 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Next.jsUse the next/image component to set the appropriate sizes. Learn more.
URL
Resource Size
Potential Savings
mclarengroup.com
1st party
1,151.3 KiB
822.1 KiB
Leicester City F.C Training Ground
<img alt="Leicester City F.C Training Ground" src="https://mclarengroup.com/_next/image/?url=https%3A%2F%2Fimages.prismic.io%…" decoding="async" data-nimg="fill" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fimages.prismic.io%2Fmclaren%2Fcfbd3115-83e…" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;">
/_next/image/?url=…
(mclarengroup.com)
348.8 KiB
174.1 KiB
The Crown Estate Apponits McLaren Construction to deliver refurbishment project
<img alt="The Crown Estate Apponits McLaren Construction to deliver refurbishment pr…" src="https://mclarengroup.com/_next/image/?url=https%3A%2F%2Fimages.prismic.io%…" decoding="async" data-nimg="fill" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fimages.prismic.io%2Fmclaren%2F2c2706ae-30a…">
/_next/image/?url=…
(mclarengroup.com)
116.7 KiB
112.5 KiB
McLaren delivers the Salvation Army New Territorial Headquarters
<img alt="McLaren delivers the Salvation Army New Territorial Headquarters" src="https://mclarengroup.com/_next/image/?url=https%3A%2F%2Fimages.prismic.io%…" decoding="async" data-nimg="fill" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fimages.prismic.io%2Fmclaren%2F63898ba9-b24…">
/_next/image/?url=…
(mclarengroup.com)
109.3 KiB
102.3 KiB
McLaren Construction rewards growth and reinforces customer relationships with …
<img alt="McLaren Construction rewards growth and reinforces customer relationships …" src="https://mclarengroup.com/_next/image/?url=https%3A%2F%2Fimages.prismic.io%…" decoding="async" data-nimg="fill" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fimages.prismic.io%2Fmclaren%2F79792fa1-641…">
/_next/image/?url=…
(mclarengroup.com)
104.0 KiB
98.3 KiB
McLaren Construction wins 'HR Team of the Year' at the 2023 Construction News W…
<img alt="McLaren Construction wins 'HR Team of the Year' at the 2023 Construction N…" src="https://mclarengroup.com/_next/image/?url=https%3A%2F%2Fimages.prismic.io%…" decoding="async" data-nimg="fill" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fimages.prismic.io%2Fmclaren%2Feb6e6b72-951…">
/_next/image/?url=…
(mclarengroup.com)
98.9 KiB
93.5 KiB
McLaren Construction Midlands and North completes multi-million Omega West Logi…
<img alt="McLaren Construction Midlands and North completes multi-million Omega West…" src="https://mclarengroup.com/_next/image/?url=https%3A%2F%2Fimages.prismic.io%…" decoding="async" data-nimg="fill" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fimages.prismic.io%2Fmclaren%2Fd328a11f-8bb…">
/_next/image/?url=…
(mclarengroup.com)
98.8 KiB
91.6 KiB
Final steelworks added to ExCel's 25,000 sqm expansion as project on track for …
<img alt="Final steelworks added to ExCel's 25,000 sqm expansion as project on track…" src="https://mclarengroup.com/_next/image/?url=https%3A%2F%2Fimages.prismic.io%…" decoding="async" data-nimg="fill" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fimages.prismic.io%2Fmclaren%2F1f5726cd-868…">
/_next/image/?url=…
(mclarengroup.com)
80.7 KiB
76.3 KiB
ExCel London
<img alt="ExCel London" src="https://mclarengroup.com/_next/image/?url=https%3A%2F%2Fimages.prismic.io%…" decoding="async" data-nimg="fill" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fimages.prismic.io%2Fmclaren%2Fc5615510-1a0…" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;">
/_next/image/?url=…
(mclarengroup.com)
194.1 KiB
73.5 KiB
prismic.io
372.1 KiB
369.9 KiB
This is us. Download our latest brochure
<img src="https://images.prismic.io/mclaren/ab9cf001-af86-415c-85eb-c6573b43d8e6_McL…" layout="fixed" width="200" height="200" objectfit="center" alt="This is us. Download our latest brochure" class="jsx-768496529f1034c1">
/mclaren/ab9cf001-…+This+is+us_Company+Brochure-1.png?auto=…
(images.prismic.io)
372.1 KiB
369.9 KiB
Defer offscreen images Potential savings of 331 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Next.jsUse the next/image component instead of <img> to automatically lazy-load images. Learn more.
URL
Resource Size
Potential Savings
mclarengroup.com
1st party
348.8 KiB
331.4 KiB
Leicester City F.C Training Ground
<img alt="Leicester City F.C Training Ground" src="https://mclarengroup.com/_next/image/?url=https%3A%2F%2Fimages.prismic.io%…" decoding="async" data-nimg="fill" sizes="100vw" srcset="/_next/image/?url=https%3A%2F%2Fimages.prismic.io%2Fmclaren%2Fcfbd3115-83e…" style="position: absolute; inset: 0px; box-sizing: border-box; padding: 0px;">
/_next/image/?url=…
(mclarengroup.com)
348.8 KiB
331.4 KiB
Avoid serving legacy JavaScript to modern browsers Potential savings of 38 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScriptTBT
URL
Potential Savings
cdn-cookieyes.com
28.8 KiB
…673e509…/banner.js
(cdn-cookieyes.com)
14.4 KiB
…673e509…/banner.js:1:39638
(cdn-cookieyes.com)
Array.prototype.filter
…673e509…/banner.js:1:39901
(cdn-cookieyes.com)
Array.prototype.find
…673e509…/banner.js:1:40066
(cdn-cookieyes.com)
Array.from
…673e509…/banner.js:1:41304
(cdn-cookieyes.com)
Array.prototype.map
…673e509…/banner.js:1:43788
(cdn-cookieyes.com)
Object.getOwnPropertyDescriptors
…673e509…/banner.js:1:44227
(cdn-cookieyes.com)
Object.keys
…673e509…/banner.js:1:75399
(cdn-cookieyes.com)
@babel/plugin-transform-regenerator
…673e509…/script.js
(cdn-cookieyes.com)
14.4 KiB
…673e509…/script.js:1:40849
(cdn-cookieyes.com)
Array.prototype.find
…673e509…/script.js:1:41014
(cdn-cookieyes.com)
Array.from
…673e509…/script.js:1:42252
(cdn-cookieyes.com)
Array.prototype.map
mclarengroup.com
1st party
9.4 KiB
…pages/_app-5236a71765b26a32.js
(mclarengroup.com)
9.3 KiB
…pages/_app-5236a71765b26a32.js:1:13028
(mclarengroup.com)
Object.keys
…chunks/560-f3ab180386a2692e.js
(mclarengroup.com)
0.0 KiB
…chunks/560-f3ab180386a2692e.js:1:43611
(mclarengroup.com)
@babel/plugin-transform-classes
…chunks/main-9e4147ff57178ce2.js
(mclarengroup.com)
0.0 KiB
…chunks/main-9e4147ff57178ce2.js:1:895
(mclarengroup.com)
@babel/plugin-transform-classes
Avoid enormous network payloads Total size was 14,746 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.LCP
URL
Transfer Size
mclarengroup.com
1st party
3,809.8 KiB
…expertise/sustainability.json?uid=expertise&uid=sustainability
(mclarengroup.com)
425.5 KiB
…sectors/hotels.json?uid=sectors&uid=hotels
(mclarengroup.com)
423.4 KiB
…sectors/industrial.json?uid=sectors&uid=industrial
(mclarengroup.com)
423.4 KiB
…expertise/health-safety.json?uid=expertise&uid=health-safety
(mclarengroup.com)
423.1 KiB
…sectors/building-safety-refurbishment.json?uid=…
(mclarengroup.com)
423.1 KiB
…expertise/social-value.json?uid=expertise&uid=social-value
(mclarengroup.com)
423.0 KiB
…sectors/education.json?uid=sectors&uid=education
(mclarengroup.com)
422.9 KiB
…sectors/offices.json?uid=sectors&uid=offices
(mclarengroup.com)
422.9 KiB
…sectors/residential.json?uid=sectors&uid=residential
(mclarengroup.com)
422.6 KiB
prismic.io
1,201.8 KiB
/mclaren/6d9adf97-….mp4
(mclaren.cdn.prismic.io)
1,201.8 KiB
Avoid an excessive DOM size 1,207 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.TBT
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
1,207
Maximum DOM Depth
FEATURED PROJECTS
<span class="jsx-1145128046 specialheading">
21
Maximum Child Elements
18th December 2023 McLaren Construction Midlands and North completes multi-mill…
<ul class="sliderTray___-vHFQ sliderAnimation___300FY carousel__slider-tray carousel_…" style="display: flex; align-items: stretch; width: 250%; flex-direction: row;" role="listbox" aria-label="carousel-slider">
15
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
Unattributable
1,075 ms
Unattributable
3,846 ms
96 ms
Unattributable
3,507 ms
84 ms
Unattributable
3,149 ms
81 ms
Unattributable
630 ms
75 ms
Unattributable
3,061 ms
72 ms
Unattributable
2,974 ms
71 ms
Unattributable
3,247 ms
71 ms
Unattributable
2,793 ms
70 ms
Unattributable
3,336 ms
67 ms
Unattributable
3,616 ms
67 ms
Unattributable
1,545 ms
66 ms
Unattributable
1,854 ms
66 ms
Unattributable
2,879 ms
64 ms
Unattributable
3,698 ms
63 ms
Unattributable
2,137 ms
62 ms
cdn-cookieyes.com
900 ms
…673e509…/script.js
(cdn-cookieyes.com)
11,309 ms
603 ms
…673e509…/script.js
(cdn-cookieyes.com)
10,936 ms
105 ms
…673e509…/script.js
(cdn-cookieyes.com)
11,209 ms
100 ms
…673e509…/script.js
(cdn-cookieyes.com)
11,041 ms
92 ms
mclarengroup.com
1st party
71 ms
…chunks/560-f3ab180386a2692e.js
(mclarengroup.com)
924 ms
71 ms
Avoid large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page. Learn how to improve CLSCLS
Element
CLS Contribution
Delivering the best places - More projects Technically ComplexLarge-scaleBIM Le…
<section style="background-image:none" class="jsx-2906080399 l-section ">
0.010
FEATURED PROJECTS ExCel London Enhancing world-class conference, event and exh…
<div class="horizontalSlider___281Ls carousel__slider carousel__slider--horizontal" aria-live="polite" tabindex="0" aria-orientation="horizontal">
0.008
Projects Key Sectors Expertise Our Company News & Content Career Zone Developme…
<ul class="jsx-1157037156">
0.000
User Timing marks and measures 7 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
Next.jsConsider using Next.js Analytics to measure your app's real-world performance. Learn more.
ReactUse the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of your components. Learn more.
Name
Type
Start Time
Duration
Next.js-before-hydration
Measure
0.00 ms
442.27 ms
Next.js-hydration
Measure
442.27 ms
32.17 ms
beforeRender
Mark
442.27 ms
routeChange
Mark
473.81 ms
afterHydrate
Mark
474.45 ms
beforeRender
Mark
813.18 ms
afterRender
Mark
825.33 ms
Initial server response time was short Root document took 50 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.FCPLCP
ReactIf you are server-side rendering any React components, consider using renderToPipeableStream() or renderToStaticNodeStream() to allow the client to receive and hydrate different parts of the markup instead of all at once. Learn more.
URL
Time Spent
mclarengroup.com
1st party
50 ms
https://mclarengroup.com
50 ms
Avoid chaining critical requests 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to avoid chaining critical requests.FCPLCP
Maximum critical path latency: 385.89 ms
Initial Navigation
https://mclarengroup.com
/fonts/sourcesanspro-regular.woff2
(mclarengroup.com)
- 71.889 ms, 26.30 KiB
/fonts/sourcesanspro-light.woff2
(mclarengroup.com)
- 50.456 ms, 25.34 KiB
/fonts/sourcesanspro-semibold.woff2
(mclarengroup.com)
- 126.279 ms, 25.99 KiB
/fonts/sourcesanspro-bold.woff2
(mclarengroup.com)
- 72.11 ms, 25.63 KiB
Largest Contentful Paint element 890 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint elementLCP
Element
div.jsx-e44a68cab95685c3 > section.jsx-2906080399 > div.jsx-3384508890 > video.jsx-3384508890
<video poster="/_next/static/media/poster-hero.41db9104.webp" playsinline="" autoplay="" muted="" loop="" width="x" height="y" class="jsx-3384508890 hero__video">
Phase
% of LCP
Timing
TTFB
26%
230 ms
Load Delay
0%
0 ms
Load Time
0%
0 ms
Render Delay
74%
650 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (24)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.FCPLCP
Next.jsUse the next/script component to defer loading of non-critical third-party scripts. Learn more.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.FCPLCP
ReactIf your build system minifies CSS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.FCPLCP
ReactIf your build system minifies JS files automatically, ensure that you are deploying the production build of your application. You can check this with the React Developer Tools extension. Learn more.
Reduce unused CSS
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.FCPLCP
Next.jsConsider setting up PurgeCSS in Next.js configuration to remove unused rules from stylesheets. Learn more.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Next.jsUse the next/image component instead of <img> to adjust image quality. Learn more.
Serve images in next-gen formats
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Next.jsUse the next/image component instead of <img> to automatically optimize image format. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.FCPLCP
Next.jsEnable compression on your Next.js server. Learn more.
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.FCPLCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.FCPLCP
ReactIf you are using React Router, minimize usage of the <Redirect> component for route navigations.
Preload key requests
Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn how to preload key requests.FCPLCP
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more about HTTP/2.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formatsLCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.LCP
Next.jsUse the next/image component and set "priority" to true to preload LCP image. Learn more.
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Next.jsConfigure caching for immutable assets and Server-side Rendered (SSR) pages. Learn more.
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.FCPLCP
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.LCP
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animationsCLS
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensionsCLS
Next.jsUse the next/image component to make sure images are always sized appropriately. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.TBT
Page didn't prevent back/forward cache restoration
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
91
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
[aria-*] attributes do not match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
Failing Elements
18th December 2023 McLaren Construction Midlands and North completes multi-mill…
<div class="horizontalSlider___281Ls carousel__slider carousel__slider--horizontal" aria-live="polite" tabindex="0" aria-orientation="horizontal">
FEATURED PROJECTS ExCel London Enhancing world-class conference, event and exh…
<div class="horizontalSlider___281Ls carousel__slider carousel__slider--horizontal" aria-live="polite" tabindex="0" aria-orientation="horizontal">
Values assigned to role="" are not valid ARIA roles.
ARIA roles enable assistive technologies to know the role of each element on the web page. If the role values are misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
Failing Elements
Technically Complex
<button aria-label="Technically Complex" role="tabpanel" class="jsx-473797557 is-active">
Large-scale
<button aria-label="Large-scale" role="tabpanel" class="jsx-473797557 ">
BIM Level 2
<button aria-label="BIM Level 2" role="tabpanel" class="jsx-473797557 ">
Public sector
<button aria-label="Public sector" role="tabpanel" class="jsx-473797557 ">
Social Value
<button aria-label="Social Value" role="tabpanel" class="jsx-473797557 ">
Highly Sustainable
<button aria-label="Highly Sustainable" role="tabpanel" class="jsx-473797557 ">
Luxury
<button aria-label="Luxury" role="tabpanel" class="jsx-473797557 ">
Full fit-out
<button aria-label="Full fit-out" role="tabpanel" class="jsx-473797557 ">
Heritage
<button aria-label="Heritage" role="tabpanel" class="jsx-473797557 ">
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
Accept
<button class="cky-btn cky-btn-accept" aria-label="Accept" data-cky-tag="accept-button" style="color: #FFFFFF; border-color: #ED8B00; background-color: #ED8B00;">
RECENT UPDATES
<span class="jsx-1037590941 specialheading">
In the news RECENT UPDATES 18th December 2023 McLaren Construction Midlands and…
<section style="background-image:none" class="jsx-2906080399 l-section l-section-light ">
Large-scale
<button aria-label="Large-scale" role="tabpanel" class="jsx-473797557 ">
Public sector
<button aria-label="Public sector" role="tabpanel" class="jsx-473797557 ">
Highly Sustainable
<button aria-label="Highly Sustainable" role="tabpanel" class="jsx-473797557 ">
Luxury
<button aria-label="Luxury" role="tabpanel" class="jsx-473797557 ">
These are opportunities to improve the legibility of your content.
Audio and video
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
Failing Elements
div.jsx-e44a68cab95685c3 > section.jsx-2906080399 > div.jsx-3384508890 > video.jsx-3384508890
<video poster="/_next/static/media/poster-hero.41db9104.webp" playsinline="" autoplay="" muted="" loop="" width="x" height="y" class="jsx-3384508890 hero__video">
These are opportunities to provide alternative content for audio and video. This may improve the experience for users with hearing or vision impairments.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (24)
Show Hide
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Elements with visible text labels have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Not applicable (31)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
[id] attributes on active, focusable elements are unique
All focusable elements must have a unique id to ensure that they're visible to assistive technologies. Learn how to fix duplicate ids.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
All heading elements contain content.
A heading with no content or inaccessible text prevent screen reader users from accessing information on the page's structure. Learn more about headings.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption.
Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the [colspan] attribute may improve the experience for screen reader users. Learn more about captions.
<td> elements in a large <table> have one or more table headers.
Screen readers have features to make navigating tables easier. Ensuring that <td> elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
91
Best practices
Browser Compatibility
Properly defines charset Error!
Required MainDocumentContent gatherer encountered an error: Protocol error (Network.getResponseBody): Request content was evicted from inspector cache
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
React
Next.js
12.2.3
core-js
core-js-global@3.22.5; core-js-global@3.22.5
Passed audits (12)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Avoids unload event listeners
The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use pagehide or visibilitychange events instead. Learn more about unload event listeners
No browser errors logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Not applicable (1)
Show Hide
Fonts with font-display: optional are preloaded
Preload optional fonts so first-time visitors may use them. Learn more about preloading fonts
100
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (11)
Show Hide
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.TBT
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more about avoiding plugins.
Not applicable (3)
Show Hide
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Tap targets are sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.