Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

liberalex.com

Liberalex - Take the liberty to enjoy your sensuality with our intimate cosmetics.

Page Load Speed

6 sec in total

First Response

228 ms

Resources Loaded

5.4 sec

Page Rendered

435 ms

liberalex.com screenshot

About Website

Welcome to liberalex.com homepage info - get ready to check Liberalex best content for Israel right away, or after learning these important things about liberalex.com

Intimate cosmetics to enhance your sensuality. Our products are unique combination of high quality ingredients, including vitamins, natural extracts and oils, gently enfolded in fresh, lush, sensual f...

Visit liberalex.com

Key Findings

We analyzed Liberalex.com page load time and found that the first response time was 228 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

liberalex.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value40.8 s

0/100

25%

SI (Speed Index)

Value25.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value32.0 s

0/100

10%

Network Requests Diagram

liberalex.com

228 ms

liberalex.com

597 ms

js

77 ms

gtm.js

126 ms

style.min.css

226 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 86% of them (118 requests) were addressed to the original Liberalex.com, 5% (7 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Liberalex.com.

Page Optimization Overview & Recommendations

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

Content Size

3.5 MB

After Optimization

3.0 MB

In fact, the total size of Liberalex.com main page is 3.5 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. 75% 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 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 211.5 kB

  • Original 255.1 kB
  • After minification 252.6 kB
  • After compression 43.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. 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 211.5 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 143.6 kB

  • Original 2.5 MB
  • After minification 2.4 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. Liberalex images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.2 kB

  • Original 420.4 kB
  • After minification 420.4 kB
  • After compression 417.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. This website has mostly compressed JavaScripts.

CSS Optimization

-42%

Potential reduce by 115.7 kB

  • Original 275.6 kB
  • After minification 275.5 kB
  • After compression 159.9 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. Liberalex.com needs all CSS files to be minified and compressed as it can save up to 115.7 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 73 (60%)

Requests Now

122

After Optimization

49

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

Accessibility Review

liberalex.com accessibility score

65

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

[aria-hidden="true"] elements contain focusable descendents

High

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

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

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

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

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

liberalex.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

liberalex.com SEO score

90

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Liberalex.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 Liberalex.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

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