Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    47% of websites

  • 85

    SEO

    Google-friendlier than
    62% of websites

sapegin.github.io

Artem Sapegin’s open source projects

Page Load Speed

184 ms in total

First Response

90 ms

Resources Loaded

93 ms

Page Rendered

1 ms

sapegin.github.io screenshot

About Website

Click here to check amazing Sapegin Github content for China. Otherwise, check out these important facts you probably never knew about sapegin.github.io

Visit sapegin.github.io

Key Findings

We analyzed Sapegin.github.io page load time and found that the first response time was 90 ms and then it took 94 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

sapegin.github.io performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.217

57/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

sapegin.github.io

90 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Sapegin.github.io and no external sources were called. The less responsive or slowest element that took the longest time to load (90 ms) belongs to the original domain Sapegin.github.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 4 B (6%)

Content Size

72 B

After Optimization

68 B

In fact, the total size of Sapegin.github.io main page is 72 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 72 B which makes up the majority of the site volume.

HTML Optimization

-6%

Potential reduce by 4 B

  • Original 72 B
  • After minification 72 B
  • After compression 68 B

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. This web page is already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

sapegin.github.io accessibility score

74

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

Best Practices

sapegin.github.io 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

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

sapegin.github.io SEO score

85

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sapegin.github.io 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 Sapegin.github.io 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

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