Tools & Wizards About Us
gleem.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

gleem.com

GLEEM Electric Powered Toothbrushes & Teeth Whitening Kits | GLEEM

Page Load Speed

1.7 sec in total

First Response

132 ms

Resources Loaded

965 ms

Page Rendered

599 ms

gleem.com screenshot

About Website

Welcome to gleem.com homepage info - get ready to check GLEEM best content for United States right away, or after learning these important things about gleem.com

GLEEM offers elegantly designed electric toothbrushes that are stylish and affordable. Finally, you don't have to spend a fortune for a smile that shines.

Visit gleem.com

Key Findings

We analyzed Gleem.com page load time and found that the first response time was 132 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

gleem.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value10,830 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

gleem.com

132 ms

gleem.com

384 ms

theme-bundle.polyfills.js

413 ms

theme-bundle.font.js

142 ms

theme-d474aa60-3072-013d-05ba-66ef57bb830b.css

94 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Gleem.com, 80% (33 requests) were made to Cdn11.bigcommerce.com and 2% (1 request) were made to Checkout-sdk.bigcommerce.com. The less responsive or slowest element that took the longest time to load (413 ms) relates to the external source Cdn11.bigcommerce.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.9 kB (2%)

Content Size

3.3 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Gleem.com main page is 3.3 MB. 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. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 53.8 kB

  • Original 67.5 kB
  • After minification 57.8 kB
  • After compression 13.7 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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 53.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.2 MB
  • After minification 3.2 MB

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. GLEEM images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 112 B

  • Original 31.9 kB
  • After minification 31.9 kB
  • After compression 31.8 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.

Requests Breakdown

Number of requests can be reduced by 8 (23%)

Requests Now

35

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gleem.com

gleem.com

132 ms

gleem.com

gleem.com

384 ms

theme-bundle.polyfills.js

theme-bundle.polyfills.js

413 ms

theme-bundle.font.js

theme-bundle.font.js

142 ms

theme-d474aa60-3072-013d-05ba-66ef57bb830b.css

theme-d474aa60-3072-013d-05ba-66ef57bb830b.css

94 ms

loader.js

loader.js

87 ms

jquery.min.js

jquery.min.js

75 ms

theme-bundle.main.js

theme-bundle.main.js

143 ms

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

150 ms

visitor_stencil.js

visitor_stencil.js

150 ms

bv.js

bv.js

152 ms

gtm.js

gtm.js

75 ms

gleem-logo_1564488920__34955.original.png

gleem-logo_1564488920__34955.original.png

35 ms

image001-22-.png

image001-22-.png

60 ms

gleem-rechargeable-toothburshes-4-colors-mobile-2x.jpg

gleem-rechargeable-toothburshes-4-colors-mobile-2x.jpg

52 ms

intro-bg.jpg

intro-bg.jpg

176 ms

gleem-black-brush-vertical.jpg

gleem-black-brush-vertical.jpg

41 ms

gleem-black-brush.jpg

gleem-black-brush.jpg

58 ms

gleem-white-brush.png

gleem-white-brush.png

66 ms

hold-behold-img.png

hold-behold-img.png

72 ms

gleem-large-break.jpg

gleem-large-break.jpg

79 ms

gleem-refills.jpg

gleem-refills.jpg

88 ms

selfie-0008.jpg

selfie-0008.jpg

87 ms

selfie-0007.jpg

selfie-0007.jpg

94 ms

selfie-0006.jpg

selfie-0006.jpg

98 ms

selfie-0005.jpg

selfie-0005.jpg

173 ms

selfie-0004.jpg

selfie-0004.jpg

173 ms

selfie-0002.jpg

selfie-0002.jpg

172 ms

selfie-0003-1.jpg

selfie-0003-1.jpg

173 ms

male-ucg.jpg

male-ucg.jpg

179 ms

selfie-0000.jpg

selfie-0000.jpg

175 ms

gleem-treat-smile-bg.jpg

gleem-treat-smile-bg.jpg

175 ms

gleem-logo.svg

gleem-logo.svg

176 ms

privacyoptions29x14.png

privacyoptions29x14.png

179 ms

smartlabel-black.png

smartlabel-black.png

180 ms

index.php

index.php

161 ms

nobot

nobot

80 ms

Gotham-Light.otf

Gotham-Light.otf

20 ms

Gotham-Bold.otf

Gotham-Bold.otf

50 ms

Gotham-Medium.otf

Gotham-Medium.otf

49 ms

Gotham-Book.otf

Gotham-Book.otf

26 ms

Accessibility Review

gleem.com accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

gleem.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

gleem.com SEO score

86

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

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 Gleem.com 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 Gleem.com 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

gleem.com

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