Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

flower-station.com

flower station フラワーステーション

Page Load Speed

5.8 sec in total

First Response

520 ms

Resources Loaded

5.1 sec

Page Rendered

241 ms

flower-station.com screenshot

About Website

Welcome to flower-station.com homepage info - get ready to check Flower Station best content right away, or after learning these important things about flower-station.com

プリザーブドフラワー、観葉植物、そのまま飾れる魔法の花束などフラワーギフトは横浜フラワーステーション

Visit flower-station.com

Key Findings

We analyzed Flower-station.com page load time and found that the first response time was 520 ms and then it took 5.3 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

flower-station.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value1.3 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.8 s

100/100

10%

Network Requests Diagram

flower-station.com

520 ms

799 ms

common.css

329 ms

css.js

330 ms

navi.js

349 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 80% of them (95 requests) were addressed to the original Flower-station.com, 8% (10 requests) were made to Static.xx.fbcdn.net and 4% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Flower-station.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 325.0 kB (24%)

Content Size

1.3 MB

After Optimization

1.0 MB

In fact, the total size of Flower-station.com main page is 1.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. 45% of websites need less resources to load. Images take 937.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 28.1 kB

  • Original 37.2 kB
  • After minification 35.6 kB
  • After compression 9.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 28.1 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 26.8 kB

  • Original 937.9 kB
  • After minification 911.2 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. Flower Station images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 221.7 kB

  • Original 306.9 kB
  • After minification 232.7 kB
  • After compression 85.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 221.7 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 48.5 kB

  • Original 59.2 kB
  • After minification 42.9 kB
  • After compression 10.8 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. Flower-station.com needs all CSS files to be minified and compressed as it can save up to 48.5 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

117

After Optimization

55

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

Accessibility Review

flower-station.com accessibility score

100

Accessibility Issues

Best Practices

flower-station.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

flower-station.com SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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