Tools & Wizards About Us
glutz.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

glutz.com

Glutz - access solutions for all requirements | Glutz

Page Load Speed

2.1 sec in total

First Response

306 ms

Resources Loaded

1.7 sec

Page Rendered

106 ms

glutz.com screenshot

About Website

Welcome to glutz.com homepage info - get ready to check Glutz best content for Switzerland right away, or after learning these important things about glutz.com

Glutz - intelligent access solutions, locks and fittings and more. ✓ Secure & convenient. Learn more!

Visit glutz.com

Key Findings

We analyzed Glutz.com page load time and found that the first response time was 306 ms and then it took 1.8 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

glutz.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.229

54/100

15%

TTI (Time to Interactive)

Value7.7 s

46/100

10%

Network Requests Diagram

glutz.com

306 ms

glutz.com

861 ms

js

74 ms

gtm.js

128 ms

css_9m8-tA3IQf8ThlLQYTTZUyEweCvyR908Tg0XCbKYOfY.css

212 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 61% of them (17 requests) were addressed to the original Glutz.com, 11% (3 requests) were made to Use.typekit.net and 11% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (861 ms) belongs to the original domain Glutz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.0 kB (34%)

Content Size

278.6 kB

After Optimization

183.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Glutz.com main page is 278.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. 20% of websites need less resources to load. Javascripts take 90.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 67.1 kB

  • Original 80.7 kB
  • After minification 67.6 kB
  • After compression 13.6 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 13.1 kB, which is 16% 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 67.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 65.1 kB
  • After minification 65.1 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. Glutz images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 3.3 kB

  • Original 90.1 kB
  • After minification 90.1 kB
  • After compression 86.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.

CSS Optimization

-57%

Potential reduce by 24.5 kB

  • Original 42.7 kB
  • After minification 42.4 kB
  • After compression 18.2 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. Glutz.com needs all CSS files to be minified and compressed as it can save up to 24.5 kB or 57% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (68%)

Requests Now

22

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Glutz. 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 from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

glutz.com

glutz.com

306 ms

glutz.com

glutz.com

861 ms

js

js

74 ms

gtm.js

gtm.js

128 ms

css_9m8-tA3IQf8ThlLQYTTZUyEweCvyR908Tg0XCbKYOfY.css

css_9m8-tA3IQf8ThlLQYTTZUyEweCvyR908Tg0XCbKYOfY.css

212 ms

font-awesome.min.css

font-awesome.min.css

33 ms

css_JsqfJgUuNO6CmCyC31b7N9RFL655TAZcahdjIeonuGc.css

css_JsqfJgUuNO6CmCyC31b7N9RFL655TAZcahdjIeonuGc.css

290 ms

css_PiDkjDyQSKuJpyt1j-h7fjzM4SyFZVVGykNXv0wRgms.css

css_PiDkjDyQSKuJpyt1j-h7fjzM4SyFZVVGykNXv0wRgms.css

297 ms

productfinder.css

productfinder.css

295 ms

css_X7bu6IeYmnWIp5SWg0VqIAA9dMBy3L53kefy-tKk8Cg.css

css_X7bu6IeYmnWIp5SWg0VqIAA9dMBy3L53kefy-tKk8Cg.css

299 ms

rwc1ycm.css

rwc1ycm.css

95 ms

logo.svg

logo.svg

332 ms

cancel.svg

cancel.svg

334 ms

p.css

p.css

47 ms

210419_Glutz_COC_Cover.jpg

210419_Glutz_COC_Cover.jpg

469 ms

js_pJOqQeLW-GMP-em3wzk8B1f9vnBk5nlHH9AYrxRLkvM.js

js_pJOqQeLW-GMP-em3wzk8B1f9vnBk5nlHH9AYrxRLkvM.js

387 ms

page.js

page.js

39 ms

js_lNb8BUt2I5IBvGOsS2Amq6ZqawG6-AU6qOCutEPUnZU.js

js_lNb8BUt2I5IBvGOsS2Amq6ZqawG6-AU6qOCutEPUnZU.js

288 ms

eu_cookie_compliance.js

eu_cookie_compliance.js

292 ms

js_OQYDpdnwFKG8Em3ULwPFbo-AYdGtjunLwfuXvW8i6r4.js

js_OQYDpdnwFKG8Em3ULwPFbo-AYdGtjunLwfuXvW8i6r4.js

323 ms

county-lang-switcher.drupal.js

county-lang-switcher.drupal.js

332 ms

arrow_down.svg

arrow_down.svg

173 ms

d

d

12 ms

d

d

101 ms

DTL_Bold.woff

DTL_Bold.woff

251 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

27 ms

sm.25.html

sm.25.html

16 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

32 ms

Accessibility Review

glutz.com accessibility score

98

Accessibility Issues

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

Links do not have a discernible name

Best Practices

glutz.com best practices score

92

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

SEO Factors

glutz.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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 Glutz.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 Glutz.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

glutz.com

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