Access lillysgem.com. Lilly's Gemstones

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value1,740 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

lillysgem.com

796 ms

webfont.js

28 ms

wp-emoji-release.min.js

30 ms

styles.css

17 ms

settings.css

30 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 78% of them (86 requests) were addressed to the original Lillysgem.com, 7% (8 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Thebeadedgarden.com. The less responsive or slowest element that took the longest time to load (995 ms) relates to the external source Thebeadedgarden.com.

Content Size

2.3 MB

After Optimization

994.3 kB

In fact, the total size of Lillysgem.com main page is 2.3 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. Javascripts take 830.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 149.2 kB

Original 177.4 kB
After minification 171.5 kB
After compression 28.1 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 149.2 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 28.0 kB

Original 654.5 kB
After minification 626.4 kB

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. Lilly Sgem images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 587.7 kB

Original 830.0 kB
After minification 794.2 kB
After compression 242.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 587.7 kB or 71% of the original size.

CSS Optimization

-85%

Potential reduce by 538.1 kB

Original 635.6 kB
After minification 555.4 kB
After compression 97.5 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. Lillysgem.com needs all CSS files to be minified and compressed as it can save up to 538.1 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

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.

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EL
Language Claimed

EL
Encoding

UTF-8

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

lillysgem.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Lilly's Gemstones - Shop

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

lillysgem.com

webfont.js

wp-emoji-release.min.js

styles.css

settings.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

lillysgem.com

webfont.js

wp-emoji-release.min.js

styles.css

settings.css

woocommerce-layout.css

woocommerce.css

prettyPhoto.css

jquery.selectBox.css

style.css

font-awesome.min.css

style.css

bootstrap.min.css

bootstrap-responsive.min.css

font-awesome.min.css

style.css

responsive.css

jquery.js

jquery-migrate.min.js

jquery.themepunch.tools.min.js

jquery.themepunch.revolution.min.js

css

analytics.js

body-bg.jpg

social-icons-mono-light-small.png

lilly-logo.png

shopping_bag_icon.png

css

css

css

transparent.png

slider2.jpg

slider.jpg

DSC153307-2.jpg

153169.jpg

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

sntaY1Q8xeij0j8FAJb2VvesZW2xOQ-xsNqO47m55DA.ttf

fontawesome-webfont.woff

fontawesome-webfont.woff

ecommerce.js

LWCjsQkB6EMdfHrEVqA1KaCWcynf_cDxXwCLxiixG1c.ttf

DXI1ORHCpsQm3Vp6mXoaTSkuG2tq91CwNPt4hF7Mg5Y.ttf