Tools & Wizards About Us
lookinglass.org screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

lookinglass.org

LookinGlass.Org :: BGP Looking Glass links collection

Page Load Speed

3.4 sec in total

First Response

158 ms

Resources Loaded

1.4 sec

Page Rendered

1.9 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 158 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

lookinglass.org performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value3,130 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

lookinglass.org

158 ms

lookinglass.org

155 ms

bootstrap.min.css

39 ms

bootstrap-theme.min.css

55 ms

main.css

27 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 39% of them (24 requests) were addressed to the original Lookinglass.org, 33% (20 requests) were made to Platform.twitter.com and 5% (3 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (909 ms) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

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

Content Size

544.8 kB

After Optimization

277.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lookinglass.org main page is 544.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. 65% of websites need less resources to load. HTML takes 301.2 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 266.5 kB

  • Original 301.2 kB
  • After minification 301.1 kB
  • After compression 34.6 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.5 kB or 88% 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

-0%

Potential reduce by 122 B

  • Original 207.1 kB
  • After minification 207.0 kB
  • After compression 206.9 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

-2%

Potential reduce by 28 B

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

Requests Breakdown

Number of requests can be reduced by 40 (70%)

Requests Now

57

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 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 27 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lookinglass.org

lookinglass.org

158 ms

lookinglass.org

lookinglass.org

155 ms

bootstrap.min.css

bootstrap.min.css

39 ms

bootstrap-theme.min.css

bootstrap-theme.min.css

55 ms

main.css

main.css

27 ms

twitter-feed.css

twitter-feed.css

29 ms

css

css

47 ms

logo.png

logo.png

42 ms

leftbar_shape.png

leftbar_shape.png

30 ms

leftbar_dobleshape.png

leftbar_dobleshape.png

45 ms

twitter-logo.png

twitter-logo.png

30 ms

Instagram-logo.png

Instagram-logo.png

27 ms

facebook-logo.png

facebook-logo.png

42 ms

blog-logo.png

blog-logo.png

45 ms

telegramlogo.png

telegramlogo.png

119 ms

TIER1.jpg

TIER1.jpg

44 ms

Asia.jpg

Asia.jpg

118 ms

Africa.jpg

Africa.jpg

118 ms

Australia-and-Oceania.jpg

Australia-and-Oceania.jpg

118 ms

Europe.jpg

Europe.jpg

118 ms

North-America.jpg

North-America.jpg

108 ms

widgets.js

widgets.js

28 ms

jquery.min.js

jquery.min.js

106 ms

bootstrap.min.js

bootstrap.min.js

28 ms

script-index.js

script-index.js

119 ms

South-America.jpg

South-America.jpg

119 ms

Multiple.jpg

Multiple.jpg

122 ms

userreport.js

userreport.js

121 ms

analytics.js

analytics.js

37 ms

tag.js

tag.js

909 ms

shape3.png

shape3.png

32 ms

shape1.png

shape1.png

32 ms

shape2.png

shape2.png

31 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

100 ms

collect

collect

94 ms

settings

settings

275 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

84 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

135 ms

js

js

167 ms

settings.js

settings.js

321 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

6 ms

embeds

embeds

30 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

14 ms

LookinGlassOrg

LookinGlassOrg

171 ms

SystemSettings.js

SystemSettings.js

299 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

3 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

2 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

19 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

26 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

39 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

38 ms

_buildManifest.js

_buildManifest.js

48 ms

_ssgManifest.js

_ssgManifest.js

48 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

9 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

9 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

4 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

9 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

9 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

19 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

8 ms

Accessibility Review

lookinglass.org accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Links do not have a discernible name

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

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

lookinglass.org

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: