Report Summary

  • 69

    Performance

    Renders faster than
    81% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

lintalist.github.io

Lintalist - Text Expander, Snippet manager, supporting searchable interactive texts to copy & paste text, run scripts, using easily exchangeable bundl...

Page Load Speed

7.7 sec in total

First Response

140 ms

Resources Loaded

1 sec

Page Rendered

6.5 sec

lintalist.github.io screenshot

About Website

Visit lintalist.github.io now to see the best up-to-date Lintalist Github content for China and also check out these interesting facts you probably never knew about lintalist.github.io

Lintalist manages searchable interactive texts to copy & paste text, run scripts, using easily exchangeable bundles - text-expander with hotkeys, full text search, plugins and scripts, gestionnaire de...

Visit lintalist.github.io

Key Findings

We analyzed Lintalist.github.io page load time and found that the first response time was 140 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

lintalist.github.io performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

95/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value730 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.288

42/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

lintalist.github.io

140 ms

style.css

86 ms

poweredbyahk.png

119 ms

lintalist.png

137 ms

lintalist65x65.gif

136 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 123.8 kB (49%)

Content Size

253.7 kB

After Optimization

129.9 kB

In fact, the total size of Lintalist.github.io main page is 253.7 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. 25% of websites need less resources to load. Images take 130.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 86.3 kB

  • Original 123.1 kB
  • After minification 123.0 kB
  • After compression 36.8 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 86.3 kB or 70% of the original size.

Image Optimization

-29%

Potential reduce by 37.5 kB

  • Original 130.6 kB
  • After minification 93.1 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. Obviously, Lintalist Github needs image optimization as it can save up to 37.5 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

17

After Optimization

17

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lintalist Github. According to our analytics all requests are already optimized.

Accessibility Review

lintalist.github.io accessibility score

85

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.

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

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

Links do not have a discernible name

Best Practices

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

SEO Factors

lintalist.github.io SEO score

96

Search Engine Optimization Advices

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 Lintalist.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 Lintalist.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 Lintalist 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: