Tools & Wizards About Us

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

glamor.cz

Krásné šaty Glamor

Page Load Speed

2.7 sec in total

First Response

374 ms

Resources Loaded

2.3 sec

Page Rendered

81 ms

About Website

Click here to check amazing Glamor content for Czech Republic. Otherwise, check out these important facts you probably never knew about glamor.cz

V e-shopu Glamor.cz najdete krásné společenské šaty mnoha střihů a velikostí od XS do 5XL, kalhotové kostýmky, šaty pro svatební maminky, šaty na svatbu, pro družičky, svědkyně i nevěsty a nechybí ani...

Visit glamor.cz

Key Findings

We analyzed Glamor.cz page load time and found that the first response time was 374 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

glamor.cz performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.309

38/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

glamor.cz

374 ms

www.glamor.cz

566 ms

open-sans.css

490 ms

font-shoptet-09.css.da98868c2b0c02771e55.css

495 ms

main-09.less.c97daf6804064e77efff.css

684 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 20% of them (4 requests) were addressed to the original Glamor.cz, 60% (12 requests) were made to Cdn.myshoptet.com and 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (888 ms) relates to the external source Ssp.imedia.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.0 kB (33%)

Content Size

157.5 kB

After Optimization

105.4 kB

  • HTML
  • JavaScript

In fact, the total size of Glamor.cz main page is 157.5 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. 35% of websites need less resources to load. Javascripts take 88.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 52.0 kB

  • Original 69.5 kB
  • After minification 62.2 kB
  • After compression 17.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. This page needs HTML code to be minified as it can gain 7.3 kB, which is 11% 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 52.0 kB or 75% of the original size.

JavaScript Optimization

-0%

Potential reduce by 25 B

  • Original 88.0 kB
  • After minification 88.0 kB
  • After compression 87.9 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 13 (76%)

Requests Now

17

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

glamor.cz 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

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

glamor.cz best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

glamor.cz SEO score

99

Search Engine Optimization Advices

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

    CS

  • Language Claimed

    CS

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glamor.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that Glamor.cz 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

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