Access freshflower.com. freshflower.com

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value0.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

freshflower.com

34 ms

bck.png

97 ms

whh_logo.gif

97 ms

box_long_header.png

97 ms

box_long_middle_noline.png

98 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 Freshflower.com, 86% (6 requests) were made to Webhostinghub.com. The less responsive or slowest element that took the longest time to load (99 ms) relates to the external source Webhostinghub.com.

Content Size

6.0 kB

After Optimization

2.8 kB

In fact, the total size of Freshflower.com main page is 6.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 4.9 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 3.2 kB

Original 4.9 kB
After minification 4.6 kB
After compression 1.7 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 3.2 kB or 65% of the original size.

Image Optimization

-1%

Potential reduce by 9 B

Original 1.1 kB
After minification 1.1 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. Freshflower images are well optimized though.

Requests Now

After Optimization

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

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

Serves images with low resolution

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freshflower.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Freshflower.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 description is not detected on the main page of Freshflower. 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: