Tools & Wizards About Us
looking.house screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% 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.1 sec in total

First Response

125 ms

Resources Loaded

763 ms

Page Rendered

231 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

616 Looking Glass points from 193 companies in 69 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 125 ms and then it took 994 ms 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

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

looking.house

125 ms

looking.house

93 ms

style.css

6 ms

js.js

17 ms

bg.png

3 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 578.7 kB (74%)

Content Size

785.6 kB

After Optimization

207.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Looking.house main page is 785.6 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 396.9 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 330.1 kB

  • Original 355.6 kB
  • After minification 351.9 kB
  • After compression 25.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 330.1 kB or 93% of the original size.

Image Optimization

-60%

Potential reduce by 238.4 kB

  • Original 396.9 kB
  • After minification 158.5 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 238.4 kB or 60% 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

92

After Optimization

92

  • Images
  • JavaScript
  • CSS

The browser has sent 92 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

125 ms

looking.house

looking.house

93 ms

style.css

style.css

6 ms

js.js

js.js

17 ms

bg.png

bg.png

3 ms

top.png

top.png

74 ms

pq_14112023.svg

pq_14112023.svg

87 ms

looking.house.svg

looking.house.svg

83 ms

fastpanel.svg

fastpanel.svg

85 ms

bar.gif

bar.gif

99 ms

ab.png

ab.png

99 ms

ar.png

ar.png

100 ms

am.png

am.png

100 ms

au.png

au.png

105 ms

at.png

at.png

104 ms

by.png

by.png

104 ms

be.png

be.png

103 ms

br.png

br.png

103 ms

bg.png

bg.png

105 ms

ca.png

ca.png

111 ms

cl.png

cl.png

105 ms

cn.png

cn.png

110 ms

co.png

co.png

110 ms

hr.png

hr.png

111 ms

cy.png

cy.png

120 ms

cz.png

cz.png

122 ms

dk.png

dk.png

133 ms

ec.png

ec.png

132 ms

ee.png

ee.png

132 ms

fi.png

fi.png

132 ms

fr.png

fr.png

138 ms

ge.png

ge.png

141 ms

de.png

de.png

143 ms

gr.png

gr.png

144 ms

hk.png

hk.png

144 ms

hu.png

hu.png

143 ms

is.png

is.png

145 ms

in.png

in.png

146 ms

id.png

id.png

149 ms

ie.png

ie.png

149 ms

1.png

1.png

134 ms

0.png

0.png

105 ms

1.png

1.png

113 ms

0.png

0.png

103 ms

0.png

0.png

92 ms

2.png

2.png

93 ms

im.png

im.png

79 ms

2.png

2.png

73 ms

1.png

1.png

72 ms

1.png

1.png

69 ms

2.png

2.png

68 ms

2.png

2.png

78 ms

0.png

0.png

87 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

72 ms

il.png

il.png

76 ms

it.png

it.png

63 ms

jp.png

jp.png

64 ms

kz.png

kz.png

63 ms

lv.png

lv.png

63 ms

lt.png

lt.png

63 ms

lu.png

lu.png

63 ms

my.png

my.png

60 ms

mx.png

mx.png

61 ms

md.png

md.png

62 ms

nl.png

nl.png

61 ms

nz.png

nz.png

62 ms

mk.png

mk.png

62 ms

no.png

no.png

61 ms

pa.png

pa.png

57 ms

pe.png

pe.png

57 ms

ph.png

ph.png

59 ms

pl.png

pl.png

58 ms

pt.png

pt.png

49 ms

ro.png

ro.png

47 ms

ru.png

ru.png

38 ms

rs.png

rs.png

37 ms

sg.png

sg.png

38 ms

sk.png

sk.png

37 ms

si.png

si.png

32 ms

za.png

za.png

30 ms

kr.png

kr.png

28 ms

es.png

es.png

29 ms

se.png

se.png

28 ms

ch.png

ch.png

29 ms

tw.png

tw.png

28 ms

th.png

th.png

26 ms

tr.png

tr.png

25 ms

ae.png

ae.png

25 ms

us.png

us.png

25 ms

ua.png

ua.png

19 ms

gb.png

gb.png

18 ms

uy.png

uy.png

18 ms

vn.png

vn.png

17 ms

cnt-gif1x1.php

cnt-gif1x1.php

19 ms

circle2.svg

circle2.svg

16 ms

cnt-gif1x1.php

cnt-gif1x1.php

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