Tools & Wizards About Us
lgtm.co screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    43% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

lgtm.co

The next step for LGTM.com: GitHub code scanning! - The GitHub Blog

Page Load Speed

1.1 sec in total

First Response

256 ms

Resources Loaded

788 ms

Page Rendered

85 ms

lgtm.co screenshot

About Website

Welcome to lgtm.co homepage info - get ready to check LGTM best content for United States right away, or after learning these important things about lgtm.co

Today, GitHub code scanning has all of LGTM.com’s key features—and more! The time has therefore come to announce the plan for the gradual deprecation of LGTM.com.

Visit lgtm.co

Key Findings

We analyzed Lgtm.co page load time and found that the first response time was 256 ms and then it took 873 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

lgtm.co performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value12,080 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

lgtm.com

256 ms

es6-promise.auto.min.js

44 ms

implement.js

83 ms

vendor-codemirror.dae159bc21d9bc1d81cb.css

69 ms

main.css

144 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that all of those requests were addressed to Lgtm.co and no external sources were called. The less responsive or slowest element that took the longest time to load (381 ms) relates to the external source Lgtm.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.6 kB (21%)

Content Size

304.9 kB

After Optimization

240.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Lgtm.co main page is 304.9 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. 45% of websites need less resources to load. Javascripts take 182.7 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 9.0 kB

  • Original 12.6 kB
  • After minification 12.0 kB
  • After compression 3.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. 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 9.0 kB or 71% of the original size.

JavaScript Optimization

-13%

Potential reduce by 24.4 kB

  • Original 182.7 kB
  • After minification 182.7 kB
  • After compression 158.3 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 24.4 kB or 13% of the original size.

CSS Optimization

-29%

Potential reduce by 31.3 kB

  • Original 109.5 kB
  • After minification 109.5 kB
  • After compression 78.3 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. Lgtm.co needs all CSS files to be minified and compressed as it can save up to 31.3 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (92%)

Requests Now

52

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lgtm.com

lgtm.com

256 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

44 ms

implement.js

implement.js

83 ms

vendor-codemirror.dae159bc21d9bc1d81cb.css

vendor-codemirror.dae159bc21d9bc1d81cb.css

69 ms

main.css

main.css

144 ms

enable_loader.js

enable_loader.js

70 ms

live.d9ea0202310c12805227.js

live.d9ea0202310c12805227.js

208 ms

vendor-_babel.72e88be97e76ff9c5b95.js

vendor-_babel.72e88be97e76ff9c5b95.js

83 ms

vendor-_material-ui.557814a490ad68d07a1a.js

vendor-_material-ui.557814a490ad68d07a1a.js

203 ms

vendor-_sentry.e14178305f705aeed9b9.js

vendor-_sentry.e14178305f705aeed9b9.js

134 ms

vendor-clsx.8934accadf633b771d57.js

vendor-clsx.8934accadf633b771d57.js

120 ms

vendor-codemirror.62884eb4e039b9c034f1.js

vendor-codemirror.62884eb4e039b9c034f1.js

205 ms

vendor-css-vendor.488c20552c2b0106d791.js

vendor-css-vendor.488c20552c2b0106d791.js

203 ms

vendor-d3-color.55895904e8800178c8c7.js

vendor-d3-color.55895904e8800178c8c7.js

204 ms

vendor-d3-interpolate.1538ae4b5b5467c4db17.js

vendor-d3-interpolate.1538ae4b5b5467c4db17.js

204 ms

vendor-d3-legacy.f1d103b039f212217cd0.js

vendor-d3-legacy.f1d103b039f212217cd0.js

289 ms

vendor-d3-scale-chromatic.cc684196bf03189e3d14.js

vendor-d3-scale-chromatic.cc684196bf03189e3d14.js

248 ms

vendor-d3.e904c70c60a7bc75c65a.js

vendor-d3.e904c70c60a7bc75c65a.js

302 ms

vendor-debounce.b07068ab73066b03d24d.js

vendor-debounce.b07068ab73066b03d24d.js

298 ms

vendor-deepmerge.7dec9c84c12f74b45763.js

vendor-deepmerge.7dec9c84c12f74b45763.js

317 ms

vendor-fuse.js.c069309110c21219fd92.js

vendor-fuse.js.c069309110c21219fd92.js

299 ms

vendor-hoist-non-react-statics.2e784200fb101041c1b9.js

vendor-hoist-non-react-statics.2e784200fb101041c1b9.js

299 ms

vendor-hyphenate-style-name.c28814b93e472f0db194.js

vendor-hyphenate-style-name.c28814b93e472f0db194.js

300 ms

vendor-is-in-browser.0fc5ba9c85cef069f8a5.js

vendor-is-in-browser.0fc5ba9c85cef069f8a5.js

300 ms

vendor-jquery.3c0a3fdd1fc2d9ff4e55.js

vendor-jquery.3c0a3fdd1fc2d9ff4e55.js

316 ms

vendor-js-cookie.4e6164c76082d2197896.js

vendor-js-cookie.4e6164c76082d2197896.js

314 ms

vendor-jss-plugin-camel-case.c8ea7b156c176da1778b.js

vendor-jss-plugin-camel-case.c8ea7b156c176da1778b.js

322 ms

vendor-jss-plugin-default-unit.7960d7b3ed3308b74c1b.js

vendor-jss-plugin-default-unit.7960d7b3ed3308b74c1b.js

323 ms

vendor-jss-plugin-global.8a8cec3862a41f8942c4.js

vendor-jss-plugin-global.8a8cec3862a41f8942c4.js

325 ms

vendor-jss-plugin-nested.a85c6d3fc599b94935de.js

vendor-jss-plugin-nested.a85c6d3fc599b94935de.js

325 ms

vendor-jss-plugin-props-sort.a4c6c382ffa1646701cb.js

vendor-jss-plugin-props-sort.a4c6c382ffa1646701cb.js

327 ms

vendor-jss-plugin-rule-value-function.c4f53159b5543c527084.js

vendor-jss-plugin-rule-value-function.c4f53159b5543c527084.js

327 ms

vendor-jss-plugin-vendor-prefixer.338b65e51b4c011118a0.js

vendor-jss-plugin-vendor-prefixer.338b65e51b4c011118a0.js

323 ms

vendor-jss.dcf1add6048168e1ea09.js

vendor-jss.dcf1add6048168e1ea09.js

344 ms

vendor-lodash.d2efdb5a03dca01db794.js

vendor-lodash.d2efdb5a03dca01db794.js

351 ms

vendor-memoize-one.49f0bce29e5d111db1c1.js

vendor-memoize-one.49f0bce29e5d111db1c1.js

356 ms

vendor-moment.ca51c1cfeb616d0b0e31.js

vendor-moment.ca51c1cfeb616d0b0e31.js

381 ms

vendor-normalize-scroll-left.83b546a5ed242db151ba.js

vendor-normalize-scroll-left.83b546a5ed242db151ba.js

327 ms

vendor-object-assign.bb546f2f6a7669ea13bf.js

vendor-object-assign.bb546f2f6a7669ea13bf.js

301 ms

vendor-process.1f83789beff1ab3b0f18.js

vendor-process.1f83789beff1ab3b0f18.js

325 ms

vendor-prop-types.9025245aa085430edd87.js

vendor-prop-types.9025245aa085430edd87.js

279 ms

vendor-react-dom.ac19f78963270bd0641c.js

vendor-react-dom.ac19f78963270bd0641c.js

349 ms

vendor-react-event-listener.ed75432adf4bc0a2fa70.js

vendor-react-event-listener.ed75432adf4bc0a2fa70.js

282 ms

vendor-react-is.2b41e0533cb00e8b8efa.js

vendor-react-is.2b41e0533cb00e8b8efa.js

276 ms

vendor-react-transition-group.f5e46b5921a3f32facef.js

vendor-react-transition-group.f5e46b5921a3f32facef.js

207 ms

vendor-react.568a8d9d353e0e327381.js

vendor-react.568a8d9d353e0e327381.js

225 ms

vendor-scheduler.5a784f6e3aecd04fd3ed.js

vendor-scheduler.5a784f6e3aecd04fd3ed.js

224 ms

vendor-tiny-warning.f4d59d60517a8a11ee9a.js

vendor-tiny-warning.f4d59d60517a8a11ee9a.js

233 ms

vendor-tslib.3a1fc9bfbd9565095d91.js

vendor-tslib.3a1fc9bfbd9565095d91.js

250 ms

vendor-warning.c8817e6a5f5d385900ad.js

vendor-warning.c8817e6a5f5d385900ad.js

200 ms

vendor-webpack.e7ca0b6ddd3ebd6a7dd5.js

vendor-webpack.e7ca0b6ddd3ebd6a7dd5.js

218 ms

error_initialising_page.js

error_initialising_page.js

178 ms

tarski-loader.gif

tarski-loader.gif

223 ms

lato-v14-latin-ext_latin-regular.woff

lato-v14-latin-ext_latin-regular.woff

192 ms

lato-v14-latin-ext_latin-300.woff

lato-v14-latin-ext_latin-300.woff

193 ms

lato-v14-latin-ext_latin-700.woff

lato-v14-latin-ext_latin-700.woff

133 ms

Accessibility Review

lgtm.co accessibility score

49

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

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

lgtm.co 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

lgtm.co SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lgtm.co can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lgtm.co 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

lgtm.co

Open Graph description is not detected on the main page of LGTM. 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: