Tools & Wizards About Us
layoffs.fyi screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

layoffs.fyi

Layoffs.fyi - Tech Layoff Tracker and Startup Layoff Lists

Page Load Speed

5.9 sec in total

First Response

80 ms

Resources Loaded

5.7 sec

Page Rendered

121 ms

layoffs.fyi screenshot

About Website

Visit layoffs.fyi now to see the best up-to-date Layoffs content for United States and also check out these interesting facts you probably never knew about layoffs.fyi

[LIVE] Tracking all tech startup layoffs — and lists of employees laid off — since COVID-19. This page is constantly being updated.

Visit layoffs.fyi

Key Findings

We analyzed Layoffs.fyi page load time and found that the first response time was 80 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

layoffs.fyi performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value36,070 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value66.1 s

0/100

10%

Network Requests Diagram

layoffs.fyi

80 ms

layoffs.fyi

180 ms

js

49 ms

style.min.css

110 ms

styles.css

114 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 62% of them (41 requests) were addressed to the original Layoffs.fyi, 11% (7 requests) were made to Airtable.com and 9% (6 requests) were made to Docs.google.com. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Docs.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 778.1 kB (42%)

Content Size

1.9 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Layoffs.fyi main page is 1.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 54.2 kB

  • Original 69.8 kB
  • After minification 61.1 kB
  • After compression 15.6 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 8.8 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 54.2 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 133 B

  • Original 59.0 kB
  • After minification 58.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Layoffs images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 718.7 kB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 963.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 718.7 kB or 43% of the original size.

CSS Optimization

-10%

Potential reduce by 5.1 kB

  • Original 51.9 kB
  • After minification 51.9 kB
  • After compression 46.7 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Layoffs.fyi has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (79%)

Requests Now

58

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Layoffs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

layoffs.fyi

layoffs.fyi

80 ms

layoffs.fyi

layoffs.fyi

180 ms

js

js

49 ms

style.min.css

style.min.css

110 ms

styles.css

styles.css

114 ms

style.css

style.css

115 ms

video-container.min.css

video-container.min.css

136 ms

font-awesome.min.css

font-awesome.min.css

139 ms

bootstrap-front.css

bootstrap-front.css

137 ms

animate.css

animate.css

141 ms

topbar_style.css

topbar_style.css

134 ms

polls-css.css

polls-css.css

135 ms

wpfront-notification-bar.min.css

wpfront-notification-bar.min.css

162 ms

style.css

style.css

188 ms

font-awesome.min.css

font-awesome.min.css

163 ms

frontend-gtag.min.js

frontend-gtag.min.js

164 ms

jquery.min.js

jquery.min.js

194 ms

jquery-migrate.min.js

jquery-migrate.min.js

166 ms

custom.js

custom.js

187 ms

tpbr_front.min.js

tpbr_front.min.js

192 ms

wpfront-notification-bar.min.js

wpfront-notification-bar.min.js

193 ms

ajax-comments.min.js

ajax-comments.min.js

193 ms

index.js

index.js

199 ms

index.js

index.js

198 ms

encoder-form.js

encoder-form.js

199 ms

tabs-custom.js

tabs-custom.js

265 ms

ta.js

ta.js

204 ms

polls-js.js

polls-js.js

265 ms

jquery.theme-main.min.js

jquery.theme-main.min.js

263 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

263 ms

responsive-menu.min.js

responsive-menu.min.js

264 ms

api.js

api.js

93 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

265 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

266 ms

wp-polyfill.min.js

wp-polyfill.min.js

266 ms

index.js

index.js

265 ms

forms.js

forms.js

285 ms

js

js

36 ms

css

css

29 ms

shrqYt5kSqMzHV9R5

shrqYt5kSqMzHV9R5

131 ms

pubchart

pubchart

1861 ms

pubchart

pubchart

2351 ms

pubchart

pubchart

5050 ms

shrCw3Tjw1XecRwX8

shrCw3Tjw1XecRwX8

67 ms

shrMt3xmtTO0p4MGT

shrMt3xmtTO0p4MGT

128 ms

arrow_down.png

arrow_down.png

54 ms

download.png

download.png

54 ms

WSJ-Logo-e1673244352458.jpg

WSJ-Logo-e1673244352458.jpg

54 ms

NewYorkTimes.svg_.png

NewYorkTimes.svg_.png

67 ms

va9Z4lja2NVIDdIAAoMR5MfuElaRB0RyklrRPXk.ttf

va9Z4lja2NVIDdIAAoMR5MfuElaRB0RyklrRPXk.ttf

42 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

104 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

107 ms

recaptcha__en.js

recaptcha__en.js

38 ms

shrCw3Tjw1XecRwX8

shrCw3Tjw1XecRwX8

65 ms

shrqYt5kSqMzHV9R5

shrqYt5kSqMzHV9R5

36 ms

shrMt3xmtTO0p4MGT

shrMt3xmtTO0p4MGT

227 ms

all.css

all.css

46 ms

455a1bf3.js

455a1bf3.js

21 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

22 ms

jquery-mod1.min.js

jquery-mod1.min.js

26 ms

jquery-ui-1.11.4.custom.mod6.min.js

jquery-ui-1.11.4.custom.mod6.min.js

31 ms

run_share.js

run_share.js

37 ms

OtAutoBlock.js

OtAutoBlock.js

31 ms

838001818-v3-ritz_chart_css_ltr.css

838001818-v3-ritz_chart_css_ltr.css

11 ms

666305051-ChartsCombinedJ2clBootstrap_bootstrap_core.js

666305051-ChartsCombinedJ2clBootstrap_bootstrap_core.js

10 ms

1038353259-ChartsExportJ2cl_j2cl_core.js

1038353259-ChartsExportJ2cl_j2cl_core.js

136 ms

Accessibility Review

layoffs.fyi accessibility score

75

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

ARIA

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.

Impact

Issue

High

ARIA IDs are not unique

Best Practices

layoffs.fyi best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

layoffs.fyi SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Layoffs.fyi can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Layoffs.fyi main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

layoffs.fyi

Open Graph data is detected on the main page of Layoffs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: