Tools & Wizards About Us

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

estele.eu

Kvepalai | Kosmetika | Grožio prekės Internetu pigiau - Estele

Page Load Speed

22.2 sec in total

First Response

947 ms

Resources Loaded

20.5 sec

Page Rendered

837 ms

About Website

Click here to check amazing Estele content. Otherwise, check out these important facts you probably never knew about estele.eu

Kosmetika, kvepalai, plaukų priežiūros produktai ir kitos originalios bei prabangios grožio priemonės internetu pigiau.

Visit estele.eu

Key Findings

We analyzed Estele.eu page load time and found that the first response time was 947 ms and then it took 21.3 sec 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

estele.eu performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value3,630 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value35.3 s

0/100

10%

Network Requests Diagram

947 ms

gtm.js

56 ms

theme-9729331133.css

983 ms

api.js

67 ms

js

100 ms

Our browser made a total of 237 requests to load all elements on the main page. We found that 84% of them (198 requests) were addressed to the original Estele.eu, 4% (10 requests) were made to Static.xx.fbcdn.net and 2% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Estele.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (14%)

Content Size

9.8 MB

After Optimization

8.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Estele.eu main page is 9.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 623.7 kB

  • Original 677.7 kB
  • After minification 513.8 kB
  • After compression 54.0 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 163.9 kB, which is 24% 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 623.7 kB or 92% of the original size.

Image Optimization

-9%

Potential reduce by 738.1 kB

  • Original 8.3 MB
  • After minification 7.6 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. Estele images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 45.2 kB

  • Original 586.5 kB
  • After minification 585.4 kB
  • After compression 541.3 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

-0%

Potential reduce by 0 B

  • Original 162.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.

Requests Breakdown

Number of requests can be reduced by 62 (28%)

Requests Now

221

After Optimization

159

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

estele.eu accessibility score

61

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

estele.eu best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

estele.eu SEO score

88

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

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

    LT

  • Language Claimed

    LT

  • Encoding

    UTF-8

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