Tools & Wizards About Us
lgtm.co screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

lgtm.co

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

Page Load Speed

1.6 sec in total

First Response

15 ms

Resources Loaded

1.1 sec

Page Rendered

486 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 15 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

lgtm.co performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value550 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

15 ms

style.min.css

342 ms

56 ms

default.min.css

89 ms

5082246

84 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lgtm.co, 7% (2 requests) were made to Cdnjs.cloudflare.com and 3% (1 request) were made to Avatars.githubusercontent.com. The less responsive or slowest element that took the longest time to load (731 ms) relates to the external source Github.blog.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.2 kB (7%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lgtm.co main page is 1.8 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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 121.1 kB

  • Original 147.5 kB
  • After minification 145.6 kB
  • After compression 26.3 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 121.1 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 4.4 kB

  • Original 1.6 MB
  • After minification 1.6 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. LGTM images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 582 B

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

CSS Optimization

-1%

Potential reduce by 117 B

  • Original 14.9 kB
  • After minification 14.9 kB
  • After compression 14.8 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (31%)

Requests Now

29

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 29 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 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

15 ms

style.min.css

style.min.css

342 ms

56 ms

default.min.css

default.min.css

89 ms

5082246

5082246

84 ms

ghcc.min.js

ghcc.min.js

87 ms

ms.analytics-web-4.js

ms.analytics-web-4.js

137 ms

48 ms

i18n.min.js

i18n.min.js

80 ms

url.min.js

url.min.js

79 ms

api-fetch.min.js

api-fetch.min.js

80 ms

site-script.js

site-script.js

84 ms

highlight.min.js

highlight.min.js

93 ms

hydro-marketing.min.js

hydro-marketing.min.js

86 ms

e-202435.js

e-202435.js

84 ms

AI-DarkMode-4.png

AI-DarkMode-4.png

87 ms

Enterprise-DarkMode-3.png

Enterprise-DarkMode-3.png

87 ms

Screenshot-2024-07-23-at-8.42.45%E2%80%AFAM.png

Screenshot-2024-07-23-at-8.42.45%E2%80%AFAM.png

90 ms

Screenshot-2024-07-23-at-8.43.47%E2%80%AFAM.png

Screenshot-2024-07-23-at-8.43.47%E2%80%AFAM.png

86 ms

Screenshot-2024-07-23-at-8.44.23%E2%80%AFAM.png

Screenshot-2024-07-23-at-8.44.23%E2%80%AFAM.png

87 ms

Screenshot-2024-07-23-at-8.46.23%E2%80%AFAM.png

Screenshot-2024-07-23-at-8.46.23%E2%80%AFAM.png

89 ms

Screenshot-2024-07-23-at-8.47.04%E2%80%AFAM.png

Screenshot-2024-07-23-at-8.47.04%E2%80%AFAM.png

89 ms

lgtm1.png

lgtm1.png

731 ms

AI-DarkMode-2.png

AI-DarkMode-2.png

89 ms

ai-survey-header.png

ai-survey-header.png

94 ms

Enterprise-LightMode-3-1.png

Enterprise-LightMode-3-1.png

91 ms

Icon-Circle.svg

Icon-Circle.svg

91 ms

readme.svg

readme.svg

93 ms

actions.svg

actions.svg

94 ms

careers.svg

careers.svg

95 ms

Accessibility Review

lgtm.co accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

Page has valid source maps

SEO Factors

lgtm.co SEO score

92

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

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 Lgtm.co 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 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 data is detected on the main page of LGTM. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: