Tools & Wizards About Us
levels.fyi screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

levels.fyi

Levels.fyi | Salaries & Tools to Level Up Your Career

Page Load Speed

1.2 sec in total

First Response

143 ms

Resources Loaded

833 ms

Page Rendered

273 ms

levels.fyi screenshot

About Website

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

Search 300k+ salaries for different companies, job titles, career levels, and locations. Explore our tools to help you get paid more!

Visit levels.fyi

Key Findings

We analyzed Levels.fyi page load time and found that the first response time was 143 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

levels.fyi performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

22/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value2,700 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.548

13/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

www.levels.fyi

143 ms

script.js

102 ms

gtm.js

145 ms

main.js

85 ms

optimize.js

125 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 39% of them (39 requests) were addressed to the original Levels.fyi, 10% (10 requests) were made to Pro.fontawesome.com and 9% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (388 ms) relates to the external source Client.crisp.chat.

Page Optimization Overview & Recommendations

Page size can be reduced by 192.2 kB (22%)

Content Size

892.2 kB

After Optimization

700.1 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-76%

Potential reduce by 185.1 kB

  • Original 245.2 kB
  • After minification 245.1 kB
  • After compression 60.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 185.1 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 5.9 kB

  • Original 288.8 kB
  • After minification 282.9 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. Levels images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 358.2 kB
  • After minification 358.2 kB
  • After compression 357.1 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 47 (62%)

Requests Now

76

After Optimization

29

  • Images
  • JavaScript
  • CSS

The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Levels. 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 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.levels.fyi

www.levels.fyi

143 ms

script.js

script.js

102 ms

gtm.js

gtm.js

145 ms

main.js

main.js

85 ms

optimize.js

optimize.js

125 ms

googlelogo-small.png

googlelogo-small.png

168 ms

N5SG09E.png

N5SG09E.png

142 ms

stripe.com

stripe.com

218 ms

logo.58b2f326.svg

logo.58b2f326.svg

223 ms

jquery.min.js

jquery.min.js

144 ms

jquery.ba-throttle-debounce.min.js

jquery.ba-throttle-debounce.min.js

154 ms

crypto-js.min.js

crypto-js.min.js

213 ms

pako_inflate.min.js

pako_inflate.min.js

318 ms

smoothscroll.js

smoothscroll.js

38 ms

topbar.js

topbar.js

75 ms

smartBanner.js

smartBanner.js

93 ms

aws-amplify-core.min.js

aws-amplify-core.min.js

142 ms

aws-amplify-auth.min.js

aws-amplify-auth.min.js

209 ms

bootstrap.min.js

bootstrap.min.js

141 ms

clipboard.min.js

clipboard.min.js

344 ms

remodal.min.js

remodal.min.js

343 ms

jquery.validate.js

jquery.validate.js

365 ms

api.js

api.js

219 ms

jquery.marquee.min.js

jquery.marquee.min.js

196 ms

jquery.animateNumber.min.js

jquery.animateNumber.min.js

104 ms

commonUtils.js

commonUtils.js

100 ms

feCommonUtils.js

feCommonUtils.js

103 ms

sponsorPlacement.js

sponsorPlacement.js

103 ms

trajectories.js

trajectories.js

121 ms

levels.js

levels.js

127 ms

suggestSomething.js

suggestSomething.js

127 ms

homePagePromoRotation.js

homePagePromoRotation.js

127 ms

newsletterAndWaitlist.js

newsletterAndWaitlist.js

135 ms

levelingStandardization.js

levelingStandardization.js

134 ms

selectorModal.js

selectorModal.js

146 ms

lib.js

lib.js

141 ms

l.js

l.js

388 ms

all.css

all.css

200 ms

robinhood.com

robinhood.com

285 ms

atlassian.com

atlassian.com

297 ms

doordash.com

doordash.com

297 ms

squareup.com

squareup.com

297 ms

zoom.us

zoom.us

336 ms

mastercard.com.au

mastercard.com.au

297 ms

css

css

127 ms

dMFqFdP.png

dMFqFdP.png

131 ms

1fsQCpu.png

1fsQCpu.png

131 ms

percentiles.webp

percentiles.webp

211 ms

boxplot.webp

boxplot.webp

287 ms

monthlypercentiles.webp

monthlypercentiles.webp

292 ms

googlelogo.png

googlelogo.png

293 ms

apple.webp

apple.webp

292 ms

google.webp

google.webp

293 ms

product-manager.png

product-manager.png

191 ms

data-scientist.png

data-scientist.png

187 ms

undraw_hiring_cyhs.svg

undraw_hiring_cyhs.svg

187 ms

wreath.png

wreath.png

198 ms

comp_percentiles.png

comp_percentiles.png

282 ms

full_logo.svg

full_logo.svg

206 ms

levelsiconfilledcolored.png

levelsiconfilledcolored.png

210 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3ig.ttf

191 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf

210 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTQ3ig.ttf

285 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTQ3ig.ttf

292 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

292 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTQ3ig.ttf

334 ms

n0wwAQK.png

n0wwAQK.png

71 ms

app-store-download.svg

app-store-download.svg

78 ms

bootstrap.min.css

bootstrap.min.css

79 ms

font

font

215 ms

api.js

api.js

196 ms

placeholder-loading.min.css

placeholder-loading.min.css

144 ms

google-play-badge.svg

google-play-badge.svg

174 ms

fa-regular-400.woff

fa-regular-400.woff

58 ms

fa-light-300.woff

fa-light-300.woff

94 ms

fa-solid-900.woff

fa-solid-900.woff

77 ms

recaptcha__en.js

recaptcha__en.js

46 ms

navbar2.js

navbar2.js

19 ms

jobFamilySelector.js

jobFamilySelector.js

19 ms

fa-regular-400.ttf

fa-regular-400.ttf

27 ms

fa-light-300.ttf

fa-light-300.ttf

12 ms

fa-solid-900.ttf

fa-solid-900.ttf

11 ms

animate.css

animate.css

3 ms

common.css

common.css

49 ms

fa-regular-400.svg

fa-regular-400.svg

32 ms

fa-light-300.svg

fa-light-300.svg

17 ms

fa-solid-900.svg

fa-solid-900.svg

30 ms

customStyles.css

customStyles.css

6 ms

homePage.css

homePage.css

6 ms

font

font

47 ms

w8gdH283Tvk__Lua32TysjIfp8uK.ttf

w8gdH283Tvk__Lua32TysjIfp8uK.ttf

8 ms

closePromoProgress.css

closePromoProgress.css

6 ms

salaryPills.css

salaryPills.css

37 ms

prompt.css

prompt.css

14 ms

reviews.css

reviews.css

4 ms

navbar.css

navbar.css

4 ms

jobFamilySelector.css

jobFamilySelector.css

4 ms

currencyLocaleSelectorModal.css

currencyLocaleSelectorModal.css

4 ms

remodal.css

remodal.css

4 ms

remodal-default-theme.css

remodal-default-theme.css

5 ms

Accessibility Review

levels.fyi accessibility score

55

Accessibility Issues

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-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

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

Form elements do not have associated labels

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

levels.fyi best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

levels.fyi SEO score

80

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

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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

levels.fyi

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