Access lilywashere.gr. Lily Was Here | Greek Fashion Style Beauty and Travel Blogger

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

lilywashere.gr

344 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Lilywashere.gr and no external sources were called. The less responsive or slowest element that took the longest time to load (344 ms) belongs to the original domain Lilywashere.gr.

Content Size

2.2 MB

After Optimization

2.0 MB

In fact, the total size of Lilywashere.gr main page is 2.2 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 863 B

Original 1.5 kB
After minification 1.5 kB
After compression 660 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 863 B or 57% of the original size.

Image Optimization

-7%

Potential reduce by 155.6 kB

Original 2.1 MB
After minification 1.9 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. Lily Was Here images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 78 B

Original 86.1 kB
After minification 86.1 kB
After compression 86.0 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.

Requests Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

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

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Page has valid source maps

Search Engine Optimization Advices

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

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 Lilywashere.gr 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 Lilywashere.gr 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 Lily Was Here. 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: