The New York Times
Insights
Google Lighthouse Performance
The Google Lighthouse performance score is a metric that measures the speed and performance of a website. It’s an overall score that ranges from 0 to 100 and is generated based on a number of different performance metrics, such as the time it takes for a website to load, the time it takes for a website to become interactive, the size of the resources used by the website, and other factors that impact the user experience.
A high performance score in Google Lighthouse indicates that a website is fast and responsive, which can lead to a better user experience and improved search engine rankings. On the other hand, a low performance score can indicate that a website is slow and unresponsive, and can negatively impact the user experience.
- Mobile Performance
- 33%
- Desktop Performance
- 36%
Core Web Vitals
Core Web Vitals are a set of specific factors that Google considers important in a webpage’s overall user experience. Core Web Vitals are made up of three specific page speed and user interaction measurements: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift.
Pass or fail?
| Mobile | Fail |
|---|---|
| Desktop | Fail |
CWV Breakdown
| Vital | Mobile | Desktop | Target |
|---|---|---|---|
| Largest Contentful Paint | 5.4 s | 5.5 s | < 2.5 s |
| First Input Delay | 4,770 ms | 1,390 ms | < 100ms |
| Cumulative Layout Shift | 0.048 | 0.02 | 0.1 |
Tracking scripts
All the tracking scripts on the site generated ~586 KB of data
A tracking script is a code snippet designed to track the flow of visitors who visit a website. Media, advertising, and analytics organisations will provide a script to add to your website that sends data directly to their servers. This data can then be used to measure goals and conversions, analyse user behaviour, and influence advertising campaigns.
Consider how much of this data you actually need and use? How often do you review the analytics data, and does this inform genuine change? Are you actively running social media campaigns? Consider pausing or removing tracking scripts that aren’t being actively used.
View details
| googletagmanager.com | 2 | 182 KB |
| c.amazon-adsystem.com | 3 | 65 KB |
| securepubads.g.doubleclick.net | 16 | 246 KB |
| hbopenbid.pubmatic.com | 1 | 197 B |
| ib.adnxs.com | 3 | 2 KB |
| tlx.3lift.com | 1 | 472 B |
| rtb.openx.net | 1 | 380 B |
| config.aps.amazon-adsystem.com | 1 | 860 B |
| aax.amazon-adsystem.com | 6 | 4 KB |
| sb.scorecardresearch.com | 4 | 2 KB |
| s.amazon-adsystem.com | 15 | 11 KB |
| image8.pubmatic.com | 2 | 1 KB |
| eb2.3lift.com | 5 | 3 KB |
| nytimes-d.openx.net | 2 | 956 B |
| cs.media.net | 1 | 691 B |
| 5290727.fls.doubleclick.net | 2 | 2 KB |
| insight.adsrvr.org | 1 | 815 B |
| cm.g.doubleclick.net | 12 | 8 KB |
| match.adsrvr.org | 7 | 6 KB |
| ssum-sec.casalemedia.com | 3 | 4 KB |
| ads.pubmatic.com | 2 | 12 KB |
| image2.pubmatic.com | 4 | 2 KB |
| ups.analytics.yahoo.com | 6 | 5 KB |
| u.openx.net | 1 | 980 B |
| dsum-sec.casalemedia.com | 5 | 5 KB |
| image6.pubmatic.com | 2 | 5 KB |
| us-u.openx.net | 3 | 1 KB |
| google.com | 1 | 467 B |
| jp-u.openx.net | 2 | 770 B |
| googleads.g.doubleclick.net | 1 | 640 B |
| pixel.tapad.com | 3 | 3 KB |
| um.simpli.fi | 1 | 989 B |
| simage2.pubmatic.com | 4 | 3 KB |
| image4.pubmatic.com | 1 | 356 B |
| aax-eu.amazon-adsystem.com | 1 | 855 B |
| pixel.rubiconproject.com | 5 | 3 KB |
| px.ads.linkedin.com | 1 | 700 B |
| simage4.pubmatic.com | 2 | 712 B |
| sync.ipredictive.com | 1 | 630 B |
| x.bidswitch.net | 1 | 235 B |
Opportunities
Remove autoplaying or preloaded media files1 video0.0 B
By removing 1 autoplaying or preloaded videos, roughly 0.0 B could be removed from the page load.
This would reduce the page transfer size by 0% and reduce the pages emissions from 1.4 grams of CO2 to 1.4 grams of CO2.
Autoplaying videos can have a negative impact on the user experience for several reasons:
- Increased data usage: Autoplaying videos can consume a lot of data, especially if they are set to play in high definition. This can be a problem for users with limited data plans or slow connections, who may experience slow or interrupted playback.
- Annoyance factor: Autoplaying videos can be annoying for users, especially if they are accompanied by sound. This can lead to a negative perception of the website and decreased engagement.
- Reduced accessibility: Autoplaying videos can be a problem for users with accessibility needs, such as users who are blind or have hearing difficulties.
- Increased page load time: Autoplaying videos can increase the overall page load time, leading to a slower user experience.
- Decreased battery life: Autoplaying videos can consume a lot of battery power, especially on mobile devices, leading to reduced battery life.
In order to minimise the impact of autoplaying videos on the user experience, it is recommended to use them sparingly and only when necessary. It is also important to provide users with the option to turn off autoplaying videos and to allow them to control the playback of videos on the page. Additionally, videos should be optimised for performance and should be accompanied by captions or transcripts to improve accessibility.
View details
Assets that need text compression enabled23 KB0.005g
By enabling text compression on 5 items, , roughly 23.1 KB could be removed from the page load.
View details
| ad-tracking.js | 9 KB | 7 KB |
| ad-tracking.js | 9 KB | 7 KB |
| ad-tracking.js | 9 KB | 7 KB |
| eventtracker-snippet.js | 3 KB | 2 KB |
| pr | 2 KB | 1 KB |
Optimise images2 MB0.446g
By optimising the following images, roughly 2 MB could be removed from the transfer size, about 32%. This would reduce the CO2 generated per page load from 1.4g grams to 0.95 grams.
Images should be optimised for the web for several reasons:
- Reduced file size: Optimizing images can result in a smaller file size, which can help to reduce the amount of data that needs to be downloaded. This can lead to faster page load times and improved performance.
- Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
- Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
- Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.
View details
| 4997763198458966905 | 407 KB | 7% | 318 KB |
| 11844870828169595759 | 259 KB | 4% | 191 KB |
| 5247407539673474141 | 252 KB | 4% | 196 KB |
| 1833086610072121988 | 245 KB | 4% | 220 KB |
| 14823162703348242362 | 221 KB | 4% | 196 KB |
| 3774400676360965938 | 193 KB | 3% | 168 KB |
| 11170470302353487380 | 170 KB | 3% | 147 KB |
| 13313744088488288806 | 149 KB | 2% | 106 KB |
| 7076880491583306224 | 130 KB | 2% | 114 KB |
| 14840528201358298462 | 127 KB | 2% | 106 KB |
| 7347196514229290628 | 124 KB | 2% | 105 KB |
| CLI_PRO_Social_Cover-threeByTwoSmallAt2X.jpg | 95 KB | 2% | 48 KB |
| 380078100487396290 | 62 KB | 1% | 48 KB |
| 7371749549331346085 | 30 KB | 0% | 22 KB |
| 12709063123019235784 | 18 KB | 0% | 13 KB |
Subset large font files125 KB0.028g
Fonts should be subsetted to reduce the file size, improve performance, and reduce emissions. Subsetting a font involves removing any characters that are not needed for a particular use case, resulting in a smaller file size and faster page load times. Some specific reasons why fonts should be subsetted include:
- Reduced file size: Subsetting a font removes any unused characters, which can result in a smaller file size. This can help to reduce the amount of data that needs to be downloaded, leading to faster page load times and lower emissions.
- Improved performance: Fonts that are subsetted are faster to load and render than fonts that are not subsetted. This can help to improve the overall performance of a website, leading to a better user experience.
Overall, subsetting fonts is a good practice for anyone looking to optimize the performance and reduce the emissions of a website of a website.
View details
| cheltenham-text-cond-normal-700.7e78f9e7e6c2e02d82592c4466929fa3.woff2 | ~29 KB | ~12 KB |
| cheltenham-normal-700.530cfb72378419eedb60da7e266ad5f1.woff2 | ~29 KB | ~11 KB |
| cheltenham-normal-300.7ea91ebd036309e1fe756ee3aab272da.woff2 | ~28 KB | ~10 KB |
| franklin-normal-700.woff | ~27 KB | ~10 KB |
| karnak-normal-400.woff2 | ~27 KB | ~10 KB |
| cheltenham-normal-300.woff2 | ~27 KB | ~10 KB |
| franklin-normal-500.woff | ~27 KB | ~9 KB |
| imperial-normal-400.6131cd77b6e216c7693ed925f4309ffc.woff2 | ~27 KB | ~9 KB |
| cheltenham-normal-200.40ccfe2cc61a71e6617e56162d49b896.woff2 | ~27 KB | ~9 KB |
| cheltenham-small-italic-400.cdfa0ec29cca8c2d2f54c79d898e15c1.woff2 | ~25 KB | ~7 KB |
| cheltenham-small-normal-700.1a0b316424cdebd18086b8dbbc768eef.woff2 | ~24 KB | ~7 KB |
| franklin-normal-700.91eaf6b5642463af4091160b4bbfdfcb.woff2 | ~21 KB | ~3 KB |
| franklin-normal-600.75739ac267f076931c6da9740386ee6b.woff2 | ~21 KB | ~3 KB |
| NYTKarnakCondensed-Bold.woff2 | ~21 KB | ~3 KB |
| franklin-normal-700.woff2 | ~20 KB | ~3 KB |
| franklin-normal-700.woff2 | ~20 KB | ~3 KB |
| franklin-normal-500.0f4aea3d462cdb64748629efcbbf36bc.woff2 | ~20 KB | ~3 KB |
| franklin-normal-500.woff2 | ~20 KB | ~2 KB |
Convert font files to woff28 KB
WOFF2 is considered to be the best font format for web use because it provides a good balance of file size and compatibility. Some specific reasons why WOFF2 is a good font format include:
- Small file size: WOFF2 is a compressed font format, which means that it has a smaller file size compared to other font formats like TTF or OTF. This is important for web use because smaller file sizes can help to reduce the amount of data that needs to be downloaded, leading to faster page load times.
- High-quality font rendering: WOFF2 provides high-quality font rendering, making it a good choice for use on the web.
It’s worth noting that WOFF2 is not the only font format that can be used on the web, and there may be cases where other formats like WOFF or TTF are more suitable, depending on the specific requirements of the website. However, for most cases, WOFF2 is considered to be the best font format for web use due to its combination of small file size, good browser support, and high-quality font rendering.
View details
| franklin-normal-700.woff | woff |
| franklin-normal-500.woff | woff |
Remove third party font files
Font files should be loaded from the same hosting as the website because
- Increased loading time: Third-party sub-resources, such as scripts, fonts, or images, need to be downloaded from a separate server before they can be displayed on the website. This can increase the overall loading time of the page, leading to a slower user experience.
- Dependence on external servers: The loading of third-party subresources is dependent on the availability and performance of the external servers that host them. If these servers are slow or unavailable, it can result in slow page loading times or even errors.
- Increased risk of security threats: Third-party subresources can introduce security risks to a website, as they can contain malicious code or be used to track user activity.
View details
| g1.nyt.com | franklin-normal-700.91eaf6b5642463af4091160b4bbfdfcb.woff2 |
| g1.nyt.com | franklin-normal-500.0f4aea3d462cdb64748629efcbbf36bc.woff2 |
| g1.nyt.com | cheltenham-normal-700.530cfb72378419eedb60da7e266ad5f1.woff2 |
| g1.nyt.com | imperial-normal-400.6131cd77b6e216c7693ed925f4309ffc.woff2 |
| g1.nyt.com | cheltenham-normal-200.40ccfe2cc61a71e6617e56162d49b896.woff2 |
| g1.nyt.com | cheltenham-small-normal-700.1a0b316424cdebd18086b8dbbc768eef.woff2 |
| g1.nyt.com | cheltenham-text-cond-normal-700.7e78f9e7e6c2e02d82592c4466929fa3.woff2 |
| g1.nyt.com | cheltenham-small-italic-400.cdfa0ec29cca8c2d2f54c79d898e15c1.woff2 |
| g1.nyt.com | cheltenham-normal-300.7ea91ebd036309e1fe756ee3aab272da.woff2 |
| g1.nyt.com | franklin-normal-600.75739ac267f076931c6da9740386ee6b.woff2 |
| fonts.gstatic.com | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 |
| fonts.gstatic.com | 6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdu3cOWxw.woff2 |
| mwcm.nyt.com | NYTKarnakCondensed-Bold.woff2 |
| mwcm.nyt.com | franklin-normal-700.woff2 |
| mwcm.nyt.com | cheltenham-normal-300.woff2 |
| g1.nyt.com | franklin-normal-700.woff |
| fonts.gstatic.com | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 |
| g1.nyt.com | karnak-normal-400.woff2 |
| g1.nyt.com | franklin-normal-500.woff |
| mwcm.nyt.com | franklin-normal-700.woff2 |
| mwcm.nyt.com | franklin-normal-500.woff2 |
| fonts.gstatic.com | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 |
First Contentful Paint
First Contentful Paint (FCP) is a performance metric that measures the time it takes for the first piece of content to be rendered on the screen when a user navigates to a web page. This content can be any visual element on the page, such as text, images, or a background color.
FCP is important because it directly affects the perceived speed of a website, and can impact user engagement and conversion rates. A faster FCP can lead to a better user experience and improved performance.
Here are a few ways you can optimise your FCP:
- Optimise images: Large, unoptimised images can slow down a page’s FCP. You can optimise images by compressing them, reducing their dimensions, and choosing the right format for each image.
- Minimise HTTP requests: Each resource requested by a web page, such as images, scripts, and stylesheets, requires a separate HTTP request. Minimising the number of HTTP requests can help to reduce the time it takes for a page to render.
- Prioritize critical content: Prioritizing critical content, such as above-the-fold content, can help to ensure that users see something on the screen quickly, even if the rest of the page is still loading.
- Reduce server response time: A slow server response time can significantly impact FCP. Optimizing server-side code and server settings can help to reduce response times and improve FCP.
- Use a performance monitoring tool: There are many tools available that can help you monitor your website’s performance, including FCP. These tools can help you identify performance issues and track your progress as you implement optimizations.
| Mobile | Desktop | |
|---|---|---|
| Score | 34% | 93% |
| Timing | 3.5 s | 0.8 s |
Largest Contentful Paint
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
| Mobile | Desktop | |
|---|---|---|
| Score | 20% | 6% |
| Timing | 5.4 s | 5.5 s |
Total Blocking Time
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.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
| Timing | 10,830 ms | 3,810 ms |
Cumulative Layout Shift
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
| Mobile | Desktop | |
|---|---|---|
| Score | 99% | 100% |
| Timing | 0.048 | 0.02 |
Speed Index
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
| Timing | 20.5 s | 8.8 s |
Time to Interactive
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 3% |
| Timing | 31.7 s | 10.8 s |
Max Potential First Input Delay
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
| Timing | 4,770 ms | 1,390 ms |
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
| Mobile | Desktop | |
|---|---|---|
| Score | 61% | 93% |
| Timing | 3.5 s | 0.8 s |
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.
| Mobile | Desktop | |
|---|---|---|
| Score | 30% | 67% |
| Insight | Potential savings of 1,920 ms | Potential savings of 500 ms |
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
| Mobile | Desktop | |
|---|---|---|
| Score | 100% | 98% |
| Insight | Potential savings of 118 KiB |
Defer offscreen images
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.
| Mobile | Desktop | |
|---|---|---|
| Score | 56% | 99% |
| Insight | Potential savings of 123 KiB | Potential savings of 87 KiB |
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
| Mobile | Desktop | |
|---|---|---|
| Score | 100% | 96% |
| Insight | Potential savings of 48 KiB |
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.
| Mobile | Desktop | |
|---|---|---|
| Score | 96% | 100% |
| Insight | Potential savings of 46 KiB | Potential savings of 46 KiB |
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| Mobile | Desktop | |
|---|---|---|
| Score | 19% | 38% |
| Insight | Potential savings of 629 KiB | Potential savings of 804 KiB |
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
| Mobile | Desktop | |
|---|---|---|
| Score | 96% | 96% |
| Insight | Potential savings of 10 KiB | Potential savings of 150 KiB |
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.
| Mobile | Desktop | |
|---|---|---|
| Score | 63% | 37% |
| Insight | Potential savings of 104 KiB | Potential savings of 1,998 KiB |
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 formats
| Mobile | Desktop | |
|---|---|---|
| Score | 50% | 100% |
| Insight | Potential savings of 176 KiB |
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.
| Mobile | Desktop | |
|---|---|---|
| Score | 100% | 99% |
| Insight | Potential savings of 40 ms |
Avoid enormous network payloads
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
| Mobile | Desktop | |
|---|---|---|
| Score | 83% | 7% |
| Insight | Total size was 2,951 KiB | Total size was 6,252 KiB |
Serve static assets with an efficient cache policy
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
| Mobile | Desktop | |
|---|---|---|
| Score | 18% | 18% |
| Insight | 24 resources found | 31 resources found |
Avoid an excessive DOM size
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
| Mobile | Desktop | |
|---|---|---|
| Score | 43% | 20% |
| Insight | 1,497 elements | 1,975 elements |
Reduce JavaScript execution time
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.
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 9% |
| Timing | 21.8 s | 9.9 s |
Minimize main-thread work
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 work
| Mobile | Desktop | |
|---|---|---|
| Score | 0% | 0% |
| Timing | 27.6 s | 15.2 s |
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.
| Mobile | Desktop | |
|---|---|---|
| Grade | Pass | Fail |
Reduce the impact of third-party code
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.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
| Insight | Third-party code blocked the main thread for 2,040 ms | Third-party code blocked the main thread for 1,460 ms |
Does not use 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.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Avoid 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().
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Insights
Carbon footprint
The carbon footprint of a website can be calculated by estimating the amount of energy consumed by the data center hosting the website, as well as the energy consumed by users accessing the site. Factors that can influence a website’s carbon footprint include the size of the site, the amount of traffic it receives, and the technology and hosting infrastructure used to host the site.
| Mobile | Desktop | |
|---|---|---|
| Grade | F | F |
| Green Hosting | Yes | Yes |
| Dirtier than | 67% | 86% |
| CO2 per page load | 0.66g | 1.4g |
| CO2 wasted per page load | ~0.2g | ~0.6g |
| Transfer size | 2.88MB | 6.11MB |
| Transfer size percentile | 63% | 82% |
| Size wasted | 804.27 KB | 2.41 MB |
Sustainable hosting
By hosting this site on a server powered by renewable energy, this page generated ~1.4grams of CO2 instead of ~1.61grams of CO2.
Sustainable web hosting refers to hosting services that are designed to minimise their impact on the environment and to promote sustainability. This can include using renewable energy sources, reducing waste and emissions, and implementing best practices for energy efficiency.
Sustainable web hosting providers aim to reduce their carbon footprint by using energy-efficient server hardware, data centres, and networking equipment, as well as implementing environmentally friendly policies and practices. For example, some providers may use renewable energy sources, such as wind or solar power, to power their data centres, or they may use high-efficiency cooling systems to reduce energy consumption.
Tracking scripts
All the tracking scripts on the site generated ~586 KB of data
A tracking script is a code snippet designed to track the flow of visitors who visit a website. Media, advertising, and analytics organisations will provide a script to add to your website that sends data directly to their servers. This data can then be used to measure goals and conversions, analyse user behaviour, and influence advertising campaigns.
Consider how much of this data you actually need and use? How often do you review the analytics data, and does this inform genuine change? Are you actively running social media campaigns? Consider pausing or removing tracking scripts that aren’t being actively used.
View details
| googletagmanager.com | 2 | 182 KB |
| c.amazon-adsystem.com | 3 | 65 KB |
| securepubads.g.doubleclick.net | 16 | 246 KB |
| hbopenbid.pubmatic.com | 1 | 197 B |
| ib.adnxs.com | 3 | 2 KB |
| tlx.3lift.com | 1 | 472 B |
| rtb.openx.net | 1 | 380 B |
| config.aps.amazon-adsystem.com | 1 | 860 B |
| aax.amazon-adsystem.com | 6 | 4 KB |
| sb.scorecardresearch.com | 4 | 2 KB |
| s.amazon-adsystem.com | 15 | 11 KB |
| image8.pubmatic.com | 2 | 1 KB |
| eb2.3lift.com | 5 | 3 KB |
| nytimes-d.openx.net | 2 | 956 B |
| cs.media.net | 1 | 691 B |
| 5290727.fls.doubleclick.net | 2 | 2 KB |
| insight.adsrvr.org | 1 | 815 B |
| cm.g.doubleclick.net | 12 | 8 KB |
| match.adsrvr.org | 7 | 6 KB |
| ssum-sec.casalemedia.com | 3 | 4 KB |
| ads.pubmatic.com | 2 | 12 KB |
| image2.pubmatic.com | 4 | 2 KB |
| ups.analytics.yahoo.com | 6 | 5 KB |
| u.openx.net | 1 | 980 B |
| dsum-sec.casalemedia.com | 5 | 5 KB |
| image6.pubmatic.com | 2 | 5 KB |
| us-u.openx.net | 3 | 1 KB |
| google.com | 1 | 467 B |
| jp-u.openx.net | 2 | 770 B |
| googleads.g.doubleclick.net | 1 | 640 B |
| pixel.tapad.com | 3 | 3 KB |
| um.simpli.fi | 1 | 989 B |
| simage2.pubmatic.com | 4 | 3 KB |
| image4.pubmatic.com | 1 | 356 B |
| aax-eu.amazon-adsystem.com | 1 | 855 B |
| pixel.rubiconproject.com | 5 | 3 KB |
| px.ads.linkedin.com | 1 | 700 B |
| simage4.pubmatic.com | 2 | 712 B |
| sync.ipredictive.com | 1 | 630 B |
| x.bidswitch.net | 1 | 235 B |
Opportunities
Remove autoplaying or preloaded media files1 video0.0 B
By removing 1 autoplaying or preloaded videos, roughly 0.0 B could be removed from the page load.
This would reduce the page transfer size by 0% and reduce the pages emissions from 1.4 grams of CO2 to 1.4 grams of CO2.
Autoplaying videos can have a negative impact on the user experience for several reasons:
- Increased data usage: Autoplaying videos can consume a lot of data, especially if they are set to play in high definition. This can be a problem for users with limited data plans or slow connections, who may experience slow or interrupted playback.
- Annoyance factor: Autoplaying videos can be annoying for users, especially if they are accompanied by sound. This can lead to a negative perception of the website and decreased engagement.
- Reduced accessibility: Autoplaying videos can be a problem for users with accessibility needs, such as users who are blind or have hearing difficulties.
- Increased page load time: Autoplaying videos can increase the overall page load time, leading to a slower user experience.
- Decreased battery life: Autoplaying videos can consume a lot of battery power, especially on mobile devices, leading to reduced battery life.
In order to minimise the impact of autoplaying videos on the user experience, it is recommended to use them sparingly and only when necessary. It is also important to provide users with the option to turn off autoplaying videos and to allow them to control the playback of videos on the page. Additionally, videos should be optimised for performance and should be accompanied by captions or transcripts to improve accessibility.
View details
Assets that need text compression enabled23 KB0.005g
By enabling text compression on 5 items, , roughly 23.1 KB could be removed from the page load.
View details
| ad-tracking.js | 9 KB | 7 KB |
| ad-tracking.js | 9 KB | 7 KB |
| ad-tracking.js | 9 KB | 7 KB |
| eventtracker-snippet.js | 3 KB | 2 KB |
| pr | 2 KB | 1 KB |
Optimise images2 MB0.446g
By optimising the following images, roughly 2 MB could be removed from the transfer size, about 32%. This would reduce the CO2 generated per page load from 1.4g grams to 0.95 grams.
Images should be optimised for the web for several reasons:
- Reduced file size: Optimizing images can result in a smaller file size, which can help to reduce the amount of data that needs to be downloaded. This can lead to faster page load times and improved performance.
- Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
- Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
- Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.
View details
| 4997763198458966905 | 407 KB | 7% | 318 KB |
| 11844870828169595759 | 259 KB | 4% | 191 KB |
| 5247407539673474141 | 252 KB | 4% | 196 KB |
| 1833086610072121988 | 245 KB | 4% | 220 KB |
| 14823162703348242362 | 221 KB | 4% | 196 KB |
| 3774400676360965938 | 193 KB | 3% | 168 KB |
| 11170470302353487380 | 170 KB | 3% | 147 KB |
| 13313744088488288806 | 149 KB | 2% | 106 KB |
| 7076880491583306224 | 130 KB | 2% | 114 KB |
| 14840528201358298462 | 127 KB | 2% | 106 KB |
| 7347196514229290628 | 124 KB | 2% | 105 KB |
| CLI_PRO_Social_Cover-threeByTwoSmallAt2X.jpg | 95 KB | 2% | 48 KB |
| 380078100487396290 | 62 KB | 1% | 48 KB |
| 7371749549331346085 | 30 KB | 0% | 22 KB |
| 12709063123019235784 | 18 KB | 0% | 13 KB |
Subset large font files125 KB0.028g
Fonts should be subsetted to reduce the file size, improve performance, and reduce emissions. Subsetting a font involves removing any characters that are not needed for a particular use case, resulting in a smaller file size and faster page load times. Some specific reasons why fonts should be subsetted include:
- Reduced file size: Subsetting a font removes any unused characters, which can result in a smaller file size. This can help to reduce the amount of data that needs to be downloaded, leading to faster page load times and lower emissions.
- Improved performance: Fonts that are subsetted are faster to load and render than fonts that are not subsetted. This can help to improve the overall performance of a website, leading to a better user experience.
Overall, subsetting fonts is a good practice for anyone looking to optimize the performance and reduce the emissions of a website of a website.
View details
| cheltenham-text-cond-normal-700.7e78f9e7e6c2e02d82592c4466929fa3.woff2 | ~29 KB | ~12 KB |
| cheltenham-normal-700.530cfb72378419eedb60da7e266ad5f1.woff2 | ~29 KB | ~11 KB |
| cheltenham-normal-300.7ea91ebd036309e1fe756ee3aab272da.woff2 | ~28 KB | ~10 KB |
| franklin-normal-700.woff | ~27 KB | ~10 KB |
| karnak-normal-400.woff2 | ~27 KB | ~10 KB |
| cheltenham-normal-300.woff2 | ~27 KB | ~10 KB |
| franklin-normal-500.woff | ~27 KB | ~9 KB |
| imperial-normal-400.6131cd77b6e216c7693ed925f4309ffc.woff2 | ~27 KB | ~9 KB |
| cheltenham-normal-200.40ccfe2cc61a71e6617e56162d49b896.woff2 | ~27 KB | ~9 KB |
| cheltenham-small-italic-400.cdfa0ec29cca8c2d2f54c79d898e15c1.woff2 | ~25 KB | ~7 KB |
| cheltenham-small-normal-700.1a0b316424cdebd18086b8dbbc768eef.woff2 | ~24 KB | ~7 KB |
| franklin-normal-700.91eaf6b5642463af4091160b4bbfdfcb.woff2 | ~21 KB | ~3 KB |
| franklin-normal-600.75739ac267f076931c6da9740386ee6b.woff2 | ~21 KB | ~3 KB |
| NYTKarnakCondensed-Bold.woff2 | ~21 KB | ~3 KB |
| franklin-normal-700.woff2 | ~20 KB | ~3 KB |
| franklin-normal-700.woff2 | ~20 KB | ~3 KB |
| franklin-normal-500.0f4aea3d462cdb64748629efcbbf36bc.woff2 | ~20 KB | ~3 KB |
| franklin-normal-500.woff2 | ~20 KB | ~2 KB |
Convert font files to woff28 KB
WOFF2 is considered to be the best font format for web use because it provides a good balance of file size and compatibility. Some specific reasons why WOFF2 is a good font format include:
- Small file size: WOFF2 is a compressed font format, which means that it has a smaller file size compared to other font formats like TTF or OTF. This is important for web use because smaller file sizes can help to reduce the amount of data that needs to be downloaded, leading to faster page load times.
- High-quality font rendering: WOFF2 provides high-quality font rendering, making it a good choice for use on the web.
It’s worth noting that WOFF2 is not the only font format that can be used on the web, and there may be cases where other formats like WOFF or TTF are more suitable, depending on the specific requirements of the website. However, for most cases, WOFF2 is considered to be the best font format for web use due to its combination of small file size, good browser support, and high-quality font rendering.
View details
| franklin-normal-700.woff | woff |
| franklin-normal-500.woff | woff |
Remove third party font files
Font files should be loaded from the same hosting as the website because
- Increased loading time: Third-party sub-resources, such as scripts, fonts, or images, need to be downloaded from a separate server before they can be displayed on the website. This can increase the overall loading time of the page, leading to a slower user experience.
- Dependence on external servers: The loading of third-party subresources is dependent on the availability and performance of the external servers that host them. If these servers are slow or unavailable, it can result in slow page loading times or even errors.
- Increased risk of security threats: Third-party subresources can introduce security risks to a website, as they can contain malicious code or be used to track user activity.
View details
| g1.nyt.com | franklin-normal-700.91eaf6b5642463af4091160b4bbfdfcb.woff2 |
| g1.nyt.com | franklin-normal-500.0f4aea3d462cdb64748629efcbbf36bc.woff2 |
| g1.nyt.com | cheltenham-normal-700.530cfb72378419eedb60da7e266ad5f1.woff2 |
| g1.nyt.com | imperial-normal-400.6131cd77b6e216c7693ed925f4309ffc.woff2 |
| g1.nyt.com | cheltenham-normal-200.40ccfe2cc61a71e6617e56162d49b896.woff2 |
| g1.nyt.com | cheltenham-small-normal-700.1a0b316424cdebd18086b8dbbc768eef.woff2 |
| g1.nyt.com | cheltenham-text-cond-normal-700.7e78f9e7e6c2e02d82592c4466929fa3.woff2 |
| g1.nyt.com | cheltenham-small-italic-400.cdfa0ec29cca8c2d2f54c79d898e15c1.woff2 |
| g1.nyt.com | cheltenham-normal-300.7ea91ebd036309e1fe756ee3aab272da.woff2 |
| g1.nyt.com | franklin-normal-600.75739ac267f076931c6da9740386ee6b.woff2 |
| fonts.gstatic.com | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 |
| fonts.gstatic.com | 6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdu3cOWxw.woff2 |
| mwcm.nyt.com | NYTKarnakCondensed-Bold.woff2 |
| mwcm.nyt.com | franklin-normal-700.woff2 |
| mwcm.nyt.com | cheltenham-normal-300.woff2 |
| g1.nyt.com | franklin-normal-700.woff |
| fonts.gstatic.com | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 |
| g1.nyt.com | karnak-normal-400.woff2 |
| g1.nyt.com | franklin-normal-500.woff |
| mwcm.nyt.com | franklin-normal-700.woff2 |
| mwcm.nyt.com | franklin-normal-500.woff2 |
| fonts.gstatic.com | 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 |
Insights
Google Lighthouse Accessibility
The accessibility score in Google Lighthouse is a metric that measures how well a website is designed for users with disabilities. The score ranges from 0 to 100, with higher scores indicating better accessibility.
Google Lighthouse evaluates a website’s accessibility based on a number of different factors, such as the presence of alternative text for images, the use of semantic HTML, the ability to navigate the page using only a keyboard, and the use of appropriate color contrasts.
A high accessibility score in Google Lighthouse indicates that a website is well-designed for users with disabilities and provides an inclusive user experience. On the other hand, a low accessibility score can indicate that a website has barriers that make it difficult or impossible for some users to access and use the content.
In automated testing, this page scored 80% for accessibility on desktop. Keep in mind that automated accessibility testing is not perfect and that manual tests, use case testing, or usability testing should be completed as well.
- Mobile Accessibility
- 99%
- Desktop Accessibility
- 96%
Opportunities
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.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
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.
| Mobile | Desktop | |
|---|---|---|
| Grade | Pass | Fail |
Insights
Google Lighthouse Best Practices
Google Lighthouse evaluates a website’s best practices based on a number of different factors, such as the use of HTTPS encryption, the use of efficient caching policies, the implementation of modern web technologies, and the avoidance of deprecated technologies.
A high best practices score in Google Lighthouse indicates that a website is well-designed and follows best practices for web development, which can lead to better performance, security, and accessibility. On the other hand, a low best practices score can indicate that a website has room for improvement in terms of following best practices.
- Mobile Best Practices
- 64%
- Desktop Best Practices
- 64%
Google Lighthouse SEO
Google Lighthouse evaluates a website’s SEO based on a number of different factors, such as the presence of title and description tags, the use of header tags, the presence of structured data, the use of image alt tags, and the use of crawlable links.
A high SEO score in Google Lighthouse indicates that a website is well-optimized for search engines, which can help to improve its visibility in search results and increase its organic traffic. On the other hand, a low SEO score can indicate that a website has room for improvement in terms of its optimization for search engines.
While a high SEO score can help to improve a website’s visibility in search results, it’s not a guarantee of higher rankings, as search engine algorithms take many other factors into account when determining the ranking of a website.
- Mobile SEO
- 98%
- Desktop SEO
- 100%
Google Lighthouse PWA
The Progressive Web App (PWA) score in Google Lighthouse is a metric that measures the quality of a website as a progressive web app. The score ranges from 0 to 100, with higher scores indicating better performance and functionality as a PWA.
A progressive web app is a type of web application that combines the best features of both web and native apps, providing users with a fast, reliable, and engaging experience on any device.
Google Lighthouse evaluates a website’s PWA performance based on several key factors, such as the availability of a service worker, the presence of a web app manifest, the ability to install the app on the home screen, and the performance of the app under poor network conditions.
- Mobile PWA
- 38%
- Desktop PWA
- 29%
Tracking scripts
All the tracking scripts on the site generated ~586 KB of data
A tracking script is a code snippet designed to track the flow of visitors who visit a website. Media, advertising, and analytics organisations will provide a script to add to your website that sends data directly to their servers. This data can then be used to measure goals and conversions, analyse user behaviour, and influence advertising campaigns.
Consider how much of this data you actually need and use? How often do you review the analytics data, and does this inform genuine change? Are you actively running social media campaigns? Consider pausing or removing tracking scripts that aren’t being actively used.
View details
| googletagmanager.com | 2 | 182 KB |
| c.amazon-adsystem.com | 3 | 65 KB |
| securepubads.g.doubleclick.net | 16 | 246 KB |
| hbopenbid.pubmatic.com | 1 | 197 B |
| ib.adnxs.com | 3 | 2 KB |
| tlx.3lift.com | 1 | 472 B |
| rtb.openx.net | 1 | 380 B |
| config.aps.amazon-adsystem.com | 1 | 860 B |
| aax.amazon-adsystem.com | 6 | 4 KB |
| sb.scorecardresearch.com | 4 | 2 KB |
| s.amazon-adsystem.com | 15 | 11 KB |
| image8.pubmatic.com | 2 | 1 KB |
| eb2.3lift.com | 5 | 3 KB |
| nytimes-d.openx.net | 2 | 956 B |
| cs.media.net | 1 | 691 B |
| 5290727.fls.doubleclick.net | 2 | 2 KB |
| insight.adsrvr.org | 1 | 815 B |
| cm.g.doubleclick.net | 12 | 8 KB |
| match.adsrvr.org | 7 | 6 KB |
| ssum-sec.casalemedia.com | 3 | 4 KB |
| ads.pubmatic.com | 2 | 12 KB |
| image2.pubmatic.com | 4 | 2 KB |
| ups.analytics.yahoo.com | 6 | 5 KB |
| u.openx.net | 1 | 980 B |
| dsum-sec.casalemedia.com | 5 | 5 KB |
| image6.pubmatic.com | 2 | 5 KB |
| us-u.openx.net | 3 | 1 KB |
| google.com | 1 | 467 B |
| jp-u.openx.net | 2 | 770 B |
| googleads.g.doubleclick.net | 1 | 640 B |
| pixel.tapad.com | 3 | 3 KB |
| um.simpli.fi | 1 | 989 B |
| simage2.pubmatic.com | 4 | 3 KB |
| image4.pubmatic.com | 1 | 356 B |
| aax-eu.amazon-adsystem.com | 1 | 855 B |
| pixel.rubiconproject.com | 5 | 3 KB |
| px.ads.linkedin.com | 1 | 700 B |
| simage4.pubmatic.com | 2 | 712 B |
| sync.ipredictive.com | 1 | 630 B |
| x.bidswitch.net | 1 | 235 B |
Cost to load
| Price per GB (USD) | $3.12 |
|---|---|
| Price per GB (Local) | 3.12 USD |
| Price to load PPV (USD) | $0.009 |
| Price to load PPV (Local) | 0.009 USD |
2022 Mobile data pricing sourced from cable.co.uk
Opportunities
Security headers to set4/6
HTTP security headers are special HTTP headers that can be added to a website’s response to help improve its security. They are important because they can help to protect a website and its users from various security threats, such as cross-site scripting (XSS) attacks, cross-site request forgery (CSRF) attacks, and other types of malicious activity.
It’s important to note, however, that implementing HTTP security headers is just one aspect of a comprehensive security strategy, and that other measures, such as regular software updates, secure coding practices, and regular security audits, are also important for maintaining a secure website.
View details
It's important to note, however, that implementing HTTP security headers is just one aspect of a comprehensive security strategy, and that other measures, such as regular software updates, secure coding practices, and regular security audits, are also important for maintaining a secure website.
Registers an unload listener
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
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Uses deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
| Insight | 2 warnings found | 2 warnings found |
Browser errors were 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
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Missing source maps for large first-party JavaScript
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.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |
Issues were logged 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.
| Mobile | Desktop | |
|---|---|---|
| Grade | Fail | Fail |