Tools & Wizards About Us
looking.house screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

looking.house

Looking Glass points: execute host, ping, traceroute and mtr commands for domain name and IPv4 or IPv6 addresses

Page Load Speed

1.3 sec in total

First Response

104 ms

Resources Loaded

812 ms

Page Rendered

374 ms

looking.house screenshot

About Website

Visit looking.house now to see the best up-to-date Looking content and also check out these interesting facts you probably never knew about looking.house

512 Looking Glass points from 178 companies in 56 countries. Execute host, ping, traceroute and mtr commands for domain name and IPv4 or IPv6 addresses. You can download 10, 100 or 1000 MB files to te...

Visit looking.house

Key Findings

We analyzed Looking.house page load time and found that the first response time was 104 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

looking.house performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

looking.house

104 ms

looking.house

63 ms

style.css

8 ms

js.js

17 ms

bg.png

171 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 85% of them (72 requests) were addressed to the original Looking.house, 4% (3 requests) were made to D.basemaps.cartocdn.com and 4% (3 requests) were made to C.basemaps.cartocdn.com. The less responsive or slowest element that took the longest time to load (302 ms) belongs to the original domain Looking.house.

Page Optimization Overview & Recommendations

Page size can be reduced by 492.0 kB (71%)

Content Size

692.8 kB

After Optimization

200.7 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Looking.house main page is 692.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. 45% of websites need less resources to load. Images take 353.2 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 283.4 kB

  • Original 306.4 kB
  • After minification 303.2 kB
  • After compression 23.0 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 283.4 kB or 93% of the original size.

Image Optimization

-56%

Potential reduce by 198.4 kB

  • Original 353.2 kB
  • After minification 154.8 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, Looking needs image optimization as it can save up to 198.4 kB or 56% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-31%

Potential reduce by 10.2 kB

  • Original 33.2 kB
  • After minification 33.2 kB
  • After compression 23.0 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. Looking.house needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 31% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

80

After Optimization

80

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

looking.house

looking.house

104 ms

looking.house

looking.house

63 ms

style.css

style.css

8 ms

js.js

js.js

17 ms

bg.png

bg.png

171 ms

watch.js

watch.js

112 ms

top.png

top.png

109 ms

pq_14112023.svg

pq_14112023.svg

124 ms

looking.house.svg

looking.house.svg

110 ms

fastpanel.svg

fastpanel.svg

141 ms

bar.gif

bar.gif

179 ms

ab.png

ab.png

142 ms

au.png

au.png

142 ms

at.png

at.png

179 ms

by.png

by.png

178 ms

be.png

be.png

179 ms

br.png

br.png

180 ms

bg.png

bg.png

181 ms

ca.png

ca.png

204 ms

cl.png

cl.png

202 ms

cn.png

cn.png

202 ms

cy.png

cy.png

204 ms

cz.png

cz.png

204 ms

dk.png

dk.png

203 ms

ec.png

ec.png

207 ms

ee.png

ee.png

212 ms

fi.png

fi.png

212 ms

fr.png

fr.png

210 ms

ge.png

ge.png

211 ms

de.png

de.png

211 ms

gr.png

gr.png

220 ms

hk.png

hk.png

221 ms

hu.png

hu.png

219 ms

is.png

is.png

221 ms

in.png

in.png

220 ms

id.png

id.png

221 ms

ie.png

ie.png

225 ms

im.png

im.png

223 ms

il.png

il.png

225 ms

it.png

it.png

224 ms

1.png

1.png

175 ms

0.png

0.png

169 ms

1.png

1.png

168 ms

0.png

0.png

160 ms

0.png

0.png

120 ms

2.png

2.png

125 ms

jp.png

jp.png

124 ms

2.png

2.png

111 ms

1.png

1.png

110 ms

1.png

1.png

127 ms

2.png

2.png

118 ms

2.png

2.png

110 ms

0.png

0.png

119 ms

kz.png

kz.png

121 ms

lv.png

lv.png

119 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

115 ms

lt.png

lt.png

91 ms

lu.png

lu.png

90 ms

my.png

my.png

90 ms

mx.png

mx.png

90 ms

md.png

md.png

64 ms

nl.png

nl.png

64 ms

nz.png

nz.png

64 ms

no.png

no.png

65 ms

pl.png

pl.png

63 ms

pt.png

pt.png

64 ms

ro.png

ro.png

42 ms

ru.png

ru.png

42 ms

rs.png

rs.png

42 ms

sg.png

sg.png

42 ms

sk.png

sk.png

43 ms

za.png

za.png

43 ms

kr.png

kr.png

39 ms

es.png

es.png

36 ms

se.png

se.png

37 ms

ch.png

ch.png

36 ms

tw.png

tw.png

37 ms

tr.png

tr.png

36 ms

ae.png

ae.png

32 ms

us.png

us.png

29 ms

ua.png

ua.png

30 ms

gb.png

gb.png

29 ms

cnt-gif1x1.php

cnt-gif1x1.php

39 ms

circle2.svg

circle2.svg

30 ms

cnt-gif1x1.php

cnt-gif1x1.php

302 ms

Accessibility Review

looking.house accessibility score

89

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

looking.house best practices score

75

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

SEO Factors

looking.house SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Looking.house 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 Looking.house 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

looking.house

Open Graph description is not detected on the main page of Looking. 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: