Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 64% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 100

    SEO

    Google-friendlier than
    96% of websites

glif.io

Glifs are tools for the Filecoin network

Page Load Speed

1.3 sec in total

First Response

237 ms

Resources Loaded

941 ms

Page Rendered

130 ms

glif.io screenshot

About Website

Click here to check amazing Glif content for Iran. Otherwise, check out these important facts you probably never knew about glif.io

An interoperable set of tools for the Filecoin network. Part of the Infinite Scroll.

Visit glif.io

Key Findings

We analyzed Glif.io page load time and found that the first response time was 237 ms and then it took 1.1 sec 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

glif.io performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

glif.io

237 ms

bootstrap.css

419 ms

jquery-1.11.0.min.js

431 ms

entypo.css

275 ms

neon.css

373 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 58% of them (11 requests) were addressed to the original Glif.io, 21% (4 requests) were made to Google-analytics.com and 11% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (569 ms) belongs to the original domain Glif.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 313.4 kB (68%)

Content Size

459.9 kB

After Optimization

146.5 kB

In fact, the total size of Glif.io main page is 459.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. 15% of websites need less resources to load. Javascripts take 292.0 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 2.5 kB

  • Original 4.0 kB
  • After minification 3.6 kB
  • After compression 1.5 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 2.5 kB or 63% of the original size.

Image Optimization

-6%

Potential reduce by 582 B

  • Original 10.5 kB
  • After minification 9.9 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. Glif images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 178.3 kB

  • Original 292.0 kB
  • After minification 272.7 kB
  • After compression 113.7 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 178.3 kB or 61% of the original size.

CSS Optimization

-86%

Potential reduce by 132.0 kB

  • Original 153.4 kB
  • After minification 124.3 kB
  • After compression 21.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. Glif.io needs all CSS files to be minified and compressed as it can save up to 132.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (63%)

Requests Now

16

After Optimization

6

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

Accessibility Review

glif.io accessibility score

83

Accessibility Issues

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

glif.io best practices score

83

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

SEO Factors

glif.io SEO score

100

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

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