Tools & Wizards About Us
lytmus.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lytmus.com

Page Load Speed

1.6 sec in total

First Response

111 ms

Resources Loaded

983 ms

Page Rendered

541 ms

lytmus.com screenshot

About Website

Visit lytmus.com now to see the best up-to-date Lytmus content and also check out these interesting facts you probably never knew about lytmus.com

Hire developers using real-world tasks, not brainteasers. Hire for Web, Ops, QA, and Data roles. Conduct take-homes and remote interviews. Try Lytmus for free.

Visit lytmus.com

Key Findings

We analyzed Lytmus.com page load time and found that the first response time was 111 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

lytmus.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value7,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

www.lytmus.com

111 ms

bootstrap.min.css

86 ms

font-awesome.min.css

69 ms

home.css

55 ms

th_icon.png

56 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lytmus.com, 76% (48 requests) were made to S3.amazonaws.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (418 ms) relates to the external source S3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 862.5 kB (37%)

Content Size

2.4 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lytmus.com main page is 2.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 23.4 kB

  • Original 30.5 kB
  • After minification 25.2 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 17% 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 23.4 kB or 77% of the original size.

Image Optimization

-29%

Potential reduce by 518.3 kB

  • Original 1.8 MB
  • After minification 1.3 MB

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. Obviously, Lytmus needs image optimization as it can save up to 518.3 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-56%

Potential reduce by 213.7 kB

  • Original 384.6 kB
  • After minification 384.0 kB
  • After compression 170.9 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 213.7 kB or 56% of the original size.

CSS Optimization

-81%

Potential reduce by 107.1 kB

  • Original 131.4 kB
  • After minification 131.3 kB
  • After compression 24.4 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. Lytmus.com needs all CSS files to be minified and compressed as it can save up to 107.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (36%)

Requests Now

44

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.lytmus.com

www.lytmus.com

111 ms

bootstrap.min.css

bootstrap.min.css

86 ms

font-awesome.min.css

font-awesome.min.css

69 ms

home.css

home.css

55 ms

th_icon.png

th_icon.png

56 ms

li_icon.png

li_icon.png

56 ms

ops.png

ops.png

118 ms

qa.png

qa.png

108 ms

backend.png

backend.png

131 ms

frontend.png

frontend.png

113 ms

data.png

data.png

116 ms

cisco.png

cisco.png

115 ms

pinterest.png

pinterest.png

145 ms

okta.png

okta.png

152 ms

affirm.png

affirm.png

170 ms

skills.png

skills.png

147 ms

jquery.min.js

jquery.min.js

181 ms

bootstrap.min.js

bootstrap.min.js

157 ms

angular.min.js

angular.min.js

222 ms

angular-route.min.js

angular-route.min.js

203 ms

angular-cookies.min.js

angular-cookies.min.js

201 ms

angular-animate.min.js

angular-animate.min.js

201 ms

lytmus.min.js

lytmus.min.js

212 ms

time_saved_resume.png

time_saved_resume.png

374 ms

time_saved_phone.png

time_saved_phone.png

376 ms

time_saved_interview.png

time_saved_interview.png

375 ms

david.jpg

david.jpg

375 ms

rails.png

rails.png

379 ms

facebook.png

facebook.png

378 ms

jeff.jpg

jeff.jpg

377 ms

cameron.jpg

cameron.jpg

375 ms

heleodoro.jpg

heleodoro.jpg

379 ms

Lato-Regular.ttf

Lato-Regular.ttf

131 ms

Lato-Medium.ttf

Lato-Medium.ttf

133 ms

Lato-Light.ttf

Lato-Light.ttf

129 ms

Lato-Thin.ttf

Lato-Thin.ttf

131 ms

Lato-Semibold.ttf

Lato-Semibold.ttf

131 ms

Lato-Bold.ttf

Lato-Bold.ttf

128 ms

Lato-Heavy.ttf

Lato-Heavy.ttf

268 ms

Montserrat-Bold.ttf

Montserrat-Bold.ttf

165 ms

Montserrat-Regular.ttf

Montserrat-Regular.ttf

223 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

223 ms

Lato-LightItalic.ttf

Lato-LightItalic.ttf

321 ms

Lato-ThinItalic.ttf

Lato-ThinItalic.ttf

227 ms

Lato-Italic.ttf

Lato-Italic.ttf

288 ms

Lato-MediumItalic.ttf

Lato-MediumItalic.ttf

335 ms

Lato-SemiboldItalic.ttf

Lato-SemiboldItalic.ttf

418 ms

Lato-BoldItalic.ttf

Lato-BoldItalic.ttf

417 ms

Lato-HeavyItalic.ttf

Lato-HeavyItalic.ttf

356 ms

analytics.js

analytics.js

83 ms

ga.js

ga.js

84 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

152 ms

fbevents.js

fbevents.js

151 ms

munchkin.js

munchkin.js

150 ms

iframe_api

iframe_api

220 ms

collect

collect

128 ms

munchkin.js

munchkin.js

62 ms

1189281991180457

1189281991180457

184 ms

visitWebPage

visitWebPage

193 ms

asset_composer.js

asset_composer.js

53 ms

collect

collect

43 ms

www-widgetapi.js

www-widgetapi.js

21 ms

ga-audiences

ga-audiences

44 ms

Accessibility Review

lytmus.com accessibility score

84

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

lytmus.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

lytmus.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Lytmus.com 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 Lytmus.com 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

lytmus.com

Open Graph description is not detected on the main page of Lytmus. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: