Tools & Wizards About Us
looloo.us screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

looloo.us

LooLoo - Automatic Toilet Freshener – LooLoo: Touchless Toilet Spray

Page Load Speed

1.4 sec in total

First Response

15 ms

Resources Loaded

933 ms

Page Rendered

413 ms

looloo.us screenshot

About Website

Click here to check amazing Loo content. Otherwise, check out these important facts you probably never knew about looloo.us

LooLoo is the world's most advanced and truly hands-free toilet freshener and nightlight. LooLoo addresses smells where they happen: in the toilet. LooLoo represents a complete revolution in how t...

Visit looloo.us

Key Findings

We analyzed Looloo.us page load time and found that the first response time was 15 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

looloo.us performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

88/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value2,470 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value24.2 s

0/100

10%

Network Requests Diagram

looloo.us

15 ms

getlooloo.com

253 ms

lazysizes.min.js

20 ms

tingle.js

65 ms

keen_slider.js

23 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Looloo.us, 47% (26 requests) were made to Getlooloo.com and 11% (6 requests) were made to Staticw2.yotpo.com. The less responsive or slowest element that took the longest time to load (380 ms) relates to the external source Cookie-bar.salessquad.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 309.1 kB (36%)

Content Size

848.7 kB

After Optimization

539.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Looloo.us main page is 848.7 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 647.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 137.7 kB

  • Original 170.7 kB
  • After minification 166.1 kB
  • After compression 33.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 137.7 kB or 81% of the original size.

JavaScript Optimization

-26%

Potential reduce by 165.4 kB

  • Original 647.8 kB
  • After minification 647.7 kB
  • After compression 482.3 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 165.4 kB or 26% of the original size.

CSS Optimization

-20%

Potential reduce by 6.0 kB

  • Original 30.2 kB
  • After minification 30.2 kB
  • After compression 24.3 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. Looloo.us needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (84%)

Requests Now

50

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

looloo.us

looloo.us

15 ms

getlooloo.com

getlooloo.com

253 ms

lazysizes.min.js

lazysizes.min.js

20 ms

tingle.js

tingle.js

65 ms

keen_slider.js

keen_slider.js

23 ms

global.js

global.js

24 ms

preloads.js

preloads.js

35 ms

load_feature-87876fa245af19cbd14aa886ed59c6aa8a27c45d24dcd7a81cf2d2323506233e.js

load_feature-87876fa245af19cbd14aa886ed59c6aa8a27c45d24dcd7a81cf2d2323506233e.js

23 ms

storefront-a2d444786d996da5634fbbaeeffe6104ee672440dfa6cdcaebfb27dceaaf9c0f.js

storefront-a2d444786d996da5634fbbaeeffe6104ee672440dfa6cdcaebfb27dceaaf9c0f.js

60 ms

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

33 ms

base.css

base.css

36 ms

keen_slider.css

keen_slider.css

41 ms

klaviyo.js

klaviyo.js

22 ms

hero_banner.css

hero_banner.css

66 ms

section_multi_item.css

section_multi_item.css

61 ms

component_carousel.js

component_carousel.js

65 ms

image_text.css

image_text.css

61 ms

custom_items.css

custom_items.css

63 ms

info_cards.css

info_cards.css

66 ms

component_search.js

component_search.js

104 ms

component_product_card.js

component_product_card.js

102 ms

contact_form.js

contact_form.js

102 ms

contactform-v2.js

contactform-v2.js

30 ms

gtm.js

gtm.js

92 ms

trekkie.storefront.e72c94e00eb9a2beb8bd60a960e285c5dc9a6f86.min.js

trekkie.storefront.e72c94e00eb9a2beb8bd60a960e285c5dc9a6f86.min.js

65 ms

shop_events_listener-a7c63dba65ccddc484f77541dc8ca437e60e1e9e297fe1c3faebf6523a0ede9b.js

shop_events_listener-a7c63dba65ccddc484f77541dc8ca437e60e1e9e297fe1c3faebf6523a0ede9b.js

60 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

81 ms

651863503

651863503

176 ms

Logo.svg

Logo.svg

70 ms

fender_analytics.21a5e7f7e70af502c5ee.js

fender_analytics.21a5e7f7e70af502c5ee.js

108 ms

static.047f24ade89e4aff54a9.js

static.047f24ade89e4aff54a9.js

107 ms

runtime.47052cf3dd870ea5c769.js

runtime.47052cf3dd870ea5c769.js

49 ms

sharedUtils.8212819f5b89555febe8.js

sharedUtils.8212819f5b89555febe8.js

71 ms

vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js

vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js

71 ms

vendors~signup_forms.2c2f6e8ccec13e3b6caf.js

vendors~signup_forms.2c2f6e8ccec13e3b6caf.js

74 ms

signup_forms.ee5c5274d631fa53e391.js

signup_forms.ee5c5274d631fa53e391.js

74 ms

component_search.css

component_search.css

31 ms

analytics.js

analytics.js

19 ms

tingle.css

tingle.css

54 ms

collect

collect

102 ms

widget.js

widget.js

64 ms

fcb_37c4523cd7a4b1877915e51c2e390483.js

fcb_37c4523cd7a4b1877915e51c2e390483.js

380 ms

widget.min.js

widget.min.js

106 ms

shopify-scevent-init.js

shopify-scevent-init.js

42 ms

fH0xwHXF4cu4p_9-ffxAwg.js

fH0xwHXF4cu4p_9-ffxAwg.js

112 ms

load

load

54 ms

shopify-scripts.js

shopify-scripts.js

104 ms

widget.css

widget.css

171 ms

i

i

16 ms

bottomline

bottomline

34 ms

app.v1.0.368.js

app.v1.0.368.js

210 ms

open_sans.css

open_sans.css

33 ms

sprite-sheet.png

sprite-sheet.png

81 ms

yotpo-widget-font.svg

yotpo-widget-font.svg

52 ms

yotpo-widget-font.woff

yotpo-widget-font.woff

51 ms

Accessibility Review

looloo.us accessibility score

100

Accessibility Issues

Best Practices

looloo.us best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

looloo.us SEO score

84

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

Links do not have descriptive text

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 Looloo.us 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 Looloo.us 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

looloo.us

Open Graph data is detected on the main page of Loo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: