Report Summary

  • 26

    Performance

    Renders faster than
    47% of other websites

  • 0

    Accessibility

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 0

    SEO

lookinglass.org

LookinGlass.Org :: BGP Looking Glass links collection

Page Load Speed

6.8 sec in total

First Response

72 ms

Resources Loaded

2.3 sec

Page Rendered

4.4 sec

lookinglass.org screenshot

About Website

Click here to check amazing Looking Lass content. Otherwise, check out these important facts you probably never knew about lookinglass.org

BGP Looking Glass links collection with IPv4, IPv6 features and Internet eXchanges. Related resources and news.

Visit lookinglass.org

Key Findings

We analyzed Lookinglass.org page load time and found that the first response time was 72 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lookinglass.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value22.9 s

0/100

10%

TBT (Total Blocking Time)

Value32,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value46.3 s

0/100

10%

Network Requests Diagram

lookinglass.org

72 ms

lookinglass.org

249 ms

bootstrap.min.css

51 ms

bootstrap-theme.min.css

68 ms

main.css

28 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 38% of them (25 requests) were addressed to the original Lookinglass.org, 20% (13 requests) were made to Platform.twitter.com and 6% (4 requests) were made to Cdn.userreport.com. The less responsive or slowest element that took the longest time to load (932 ms) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 442.7 kB (61%)

Content Size

723.8 kB

After Optimization

281.1 kB

In fact, the total size of Lookinglass.org main page is 723.8 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. 60% of websites need less resources to load. Javascripts take 386.4 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 266.1 kB

  • Original 300.3 kB
  • After minification 300.2 kB
  • After compression 34.2 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 266.1 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 924 B

  • Original 35.2 kB
  • After minification 34.3 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. Looking Lass images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 175.2 kB

  • Original 386.4 kB
  • After minification 386.4 kB
  • After compression 211.2 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 175.2 kB or 45% of the original size.

CSS Optimization

-27%

Potential reduce by 513 B

  • Original 1.9 kB
  • After minification 1.9 kB
  • After compression 1.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. Lookinglass.org needs all CSS files to be minified and compressed as it can save up to 513 B or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (67%)

Requests Now

58

After Optimization

19

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

Best Practices

lookinglass.org best practices score

67

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

Browser errors were logged to the console

SEO Factors

lookinglass.org SEO score

0

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 Lookinglass.org 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 Lookinglass.org 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 Looking Lass. 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: