Tools & Wizards About Us
piece-flower.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

piece-flower.com

Pièce Associates

Page Load Speed

3.6 sec in total

First Response

802 ms

Resources Loaded

2.7 sec

Page Rendered

125 ms

piece-flower.com screenshot

About Website

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

ピエス アソシエーツはFloral,Food,Fashionの3つのアプローチから、より上質で心地よい暮らしをみなさまにご提案いたします

Visit piece-flower.com

Key Findings

We analyzed Piece-flower.com page load time and found that the first response time was 802 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

piece-flower.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

piece-flower.com

802 ms

smoothScroll.js

348 ms

smartRollover.js

373 ms

style.css

360 ms

menu.css

361 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 83% of them (24 requests) were addressed to the original Piece-flower.com, 7% (2 requests) were made to Staticxx.facebook.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Piece-flower.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.0 kB (12%)

Content Size

449.5 kB

After Optimization

397.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Piece-flower.com main page is 449.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 415.7 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 13.3 kB

  • Original 19.3 kB
  • After minification 18.6 kB
  • After compression 5.9 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 13.3 kB or 69% of the original size.

Image Optimization

-7%

Potential reduce by 27.4 kB

  • Original 415.7 kB
  • After minification 388.3 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. Piece Flower images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 2.1 kB

  • Original 3.0 kB
  • After minification 2.0 kB
  • After compression 876 B

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 2.1 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 9.2 kB

  • Original 11.5 kB
  • After minification 7.4 kB
  • After compression 2.3 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. Piece-flower.com needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (11%)

Requests Now

27

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

piece-flower.com

piece-flower.com

802 ms

smoothScroll.js

smoothScroll.js

348 ms

smartRollover.js

smartRollover.js

373 ms

style.css

style.css

360 ms

menu.css

menu.css

361 ms

jquery.min.js

jquery.min.js

9 ms

reset.css

reset.css

191 ms

base.css

base.css

365 ms

header-logo.jpg

header-logo.jpg

191 ms

nv-bg.jpg

nv-bg.jpg

181 ms

nv-home_off.jpg

nv-home_off.jpg

170 ms

nv-flower_off.jpg

nv-flower_off.jpg

181 ms

nv-cafe_off.jpg

nv-cafe_off.jpg

361 ms

nv-order_off.jpg

nv-order_off.jpg

339 ms

nv-shop_off.jpg

nv-shop_off.jpg

376 ms

nv-blog_off.jpg

nv-blog_off.jpg

377 ms

content-bg.jpg

content-bg.jpg

937 ms

topimg1.jpg

topimg1.jpg

378 ms

topimg2.jpg

topimg2.jpg

1009 ms

topimg3.jpg

topimg3.jpg

1079 ms

topimg4.jpg

topimg4.jpg

905 ms

topimg5.jpg

topimg5.jpg

1270 ms

top-intro.jpg

top-intro.jpg

566 ms

top-cafenews.jpg

top-cafenews.jpg

763 ms

allow.jpg

allow.jpg

953 ms

sdk.js

sdk.js

161 ms

90 ms

xd_arbiter.php

xd_arbiter.php

157 ms

xd_arbiter.php

xd_arbiter.php

268 ms

Accessibility Review

piece-flower.com accessibility score

79

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

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

Impact

Issue

High

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

piece-flower.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

piece-flower.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Piece-flower.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 Piece-flower.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

piece-flower.com

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