Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

glamyr.by

glamyr.by

Page Load Speed

6.6 sec in total

First Response

640 ms

Resources Loaded

4.7 sec

Page Rendered

1.3 sec

glamyr.by screenshot

About Website

Click here to check amazing Glamyr content for Belarus. Otherwise, check out these important facts you probably never knew about glamyr.by

Косметика в Минске | Крема | Маски | Макияж | Шампуни | Краски для волос | Интернет магазин косметики ГЛАМУР.BY

Visit glamyr.by

Key Findings

We analyzed Glamyr.by page load time and found that the first response time was 640 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Glamyr.by rating and web reputation

Performance Metrics

glamyr.by performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.0 s

87/100

10%

Network Requests Diagram

glamyr.by

640 ms

color.css

310 ms

main.css

305 ms

ie.css

316 ms

jquery-1.6.4.min.js

464 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 83% of them (115 requests) were addressed to the original Glamyr.by, 6% (8 requests) were made to Glamyr.shop.by and 4% (5 requests) were made to Consultsystems.ru. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Glamyr.shop.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 817.5 kB (14%)

Content Size

6.0 MB

After Optimization

5.2 MB

In fact, the total size of Glamyr.by main page is 6.0 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. 50% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 137.3 kB

  • Original 161.1 kB
  • After minification 148.2 kB
  • After compression 23.8 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.3 kB or 85% of the original size.

Image Optimization

-7%

Potential reduce by 366.1 kB

  • Original 5.4 MB
  • After minification 5.1 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. Glamyr images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 179.6 kB

  • Original 273.7 kB
  • After minification 240.5 kB
  • After compression 94.2 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 179.6 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 134.5 kB

  • Original 158.9 kB
  • After minification 115.4 kB
  • After compression 24.4 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. Glamyr.by needs all CSS files to be minified and compressed as it can save up to 134.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (24%)

Requests Now

136

After Optimization

104

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

Accessibility Review

glamyr.by accessibility score

84

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

glamyr.by 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

SEO Factors

glamyr.by SEO score

92

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glamyr.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Glamyr.by main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Glamyr. 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: