Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

glampire.net

Faberlic official website, product information, selection of a Registered Member, news, help with product selection | Faberlic

Page Load Speed

369 ms in total

First Response

98 ms

Resources Loaded

173 ms

Page Rendered

98 ms

glampire.net screenshot

About Website

Welcome to glampire.net homepage info - get ready to check Glampire best content right away, or after learning these important things about glampire.net

You can find the information about our products, select a Registered Member, read news, and choose products on the official Faberlic website.

Visit glampire.net

Key Findings

We analyzed Glampire.net page load time and found that the first response time was 98 ms and then it took 271 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

glampire.net performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value22.6 s

0/100

10%

TBT (Total Blocking Time)

Value5,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.72

6/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

glampire.net

98 ms

singlepage.css

16 ms

logo-a.svg

9 ms

proximanova-bold-webfont.woff

17 ms

proximanova-sbold-webfont.woff

21 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 14% of them (1 request) were addressed to the original Glampire.net, 86% (6 requests) were made to Securendn.a.ssl.fastly.net. The less responsive or slowest element that took the longest time to load (98 ms) belongs to the original domain Glampire.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.6 kB (85%)

Content Size

16.1 kB

After Optimization

2.5 kB

In fact, the total size of Glampire.net main page is 16.1 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. Only 10% of websites need less resources to load. CSS take 15.4 kB which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 326 B

  • Original 689 B
  • After minification 662 B
  • After compression 363 B

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 326 B or 47% of the original size.

CSS Optimization

-86%

Potential reduce by 13.3 kB

  • Original 15.4 kB
  • After minification 13.9 kB
  • After compression 2.1 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. Glampire.net needs all CSS files to be minified and compressed as it can save up to 13.3 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Glampire. According to our analytics all requests are already optimized.

Accessibility Review

glampire.net accessibility score

66

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

glampire.net 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

Missing source maps for large first-party JavaScript

SEO Factors

glampire.net SEO score

77

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

High

Document doesn't have a valid hreflang

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glampire.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Glampire.net main page’s claimed encoding is . 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 Glampire. 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: