6.8 sec in total
72 ms
2.3 sec
4.4 sec
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.orgWe 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.
lookinglass.org performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.5 s
37/100
25%
Value22.9 s
0/100
10%
Value32,500 ms
0/100
30%
Value0.004
100/100
15%
Value46.3 s
0/100
10%
72 ms
249 ms
51 ms
68 ms
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 size can be reduced by 442.7 kB (61%)
723.8 kB
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.
Potential reduce by 266.1 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.
Potential reduce by 924 B
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.
Potential reduce by 175.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.
Potential reduce by 513 B
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.
Number of requests can be reduced by 39 (67%)
58
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.
lookinglass.org
72 ms
lookinglass.org
249 ms
bootstrap.min.css
51 ms
bootstrap-theme.min.css
68 ms
main.css
28 ms
twitter-feed.css
82 ms
css
59 ms
logo.png
49 ms
leftbar_shape.png
72 ms
leftbar_dobleshape.png
38 ms
twitter-logo.png
40 ms
Instagram-logo.png
187 ms
facebook-logo.png
49 ms
blog-logo.png
56 ms
telegramlogo.png
60 ms
TIER1.jpg
185 ms
Asia.jpg
62 ms
Africa.jpg
61 ms
Australia-and-Oceania.jpg
64 ms
Europe.jpg
70 ms
North-America.jpg
148 ms
email-decode.min.js
123 ms
widgets.js
464 ms
jquery.min.js
133 ms
bootstrap.min.js
11 ms
script-index.js
122 ms
South-America.jpg
121 ms
Multiple.jpg
284 ms
shape3.png
162 ms
shape1.png
41 ms
shape2.png
172 ms
userreport.js
165 ms
analytics.js
163 ms
tag.js
932 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrcVIT9d4cw.woff
216 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d4cw.woff
217 ms
collect
176 ms
settings.js
297 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
219 ms
settings
123 ms
SystemSettings.js
281 ms
server.html
53 ms
hit.gif
77 ms
button.d2f864f87f544dc0c11d7d712a191c1f.js
50 ms
horizon_timeline.a7991bb824d62c8d5038ddd875db8389.js
69 ms
embeds
46 ms
embeds
34 ms
follow_button.7dae38096d06923d683a2a807172322a.en.html
59 ms
LookinGlassOrg
288 ms
adform
222 ms
pixel
37 ms
analytics-tags.js
4 ms
pixel
160 ms
adform
161 ms
polyfills-57d3feabe8bfd4ee389c.js
39 ms
runtime-eb61dff4a84b8f906e6b.js
40 ms
modules.c7def0268c66f6a548ed.js
62 ms
main-e9db78f5e7b3d83edd5e.js
59 ms
_app-446fb4a338b215deec8c.js
94 ms
%5BscreenName%5D-c8b4c96951cf24f547b4.js
94 ms
_buildManifest.js
121 ms
_ssgManifest.js
120 ms
receive
100 ms
advert.gif
647 ms
sync_cookie_image_decide
127 ms
lookinglass.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lookinglass.org SEO score
EN
EN
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.
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: