Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

very-very.net

町田市の花屋[フラワーショップヴェリィヴェリィ]開店祝い,アレンジメント,スタンド花,プリザーブドフラワー

Page Load Speed

6.6 sec in total

First Response

551 ms

Resources Loaded

5.5 sec

Page Rendered

564 ms

very-very.net screenshot

About Website

Click here to check amazing Very content. Otherwise, check out these important facts you probably never knew about very-very.net

東京都町田市の花屋、フラワーショップヴェリィヴェリィでは季節の花を随時取り揃え、お誕生日、お祝い、お見舞い、お悔やみなど花ギフトに関する様々なフラワーアレンジメントや花束などの販売や通販を行っています。TEL042-798-6467

Visit very-very.net

Key Findings

We analyzed Very-very.net page load time and found that the first response time was 551 ms and then it took 6.1 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

very-very.net performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.477

18/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

very-very.net

551 ms

www.very-very.net

754 ms

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.1FlClNpo4U.css

865 ms

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

898 ms

ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js

359 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 68% of them (49 requests) were addressed to the original Very-very.net, 25% (18 requests) were made to Web.xaas.jp and 7% (5 requests) were made to Ssl.xaas.jp. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Very-very.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 415.4 kB (48%)

Content Size

868.0 kB

After Optimization

452.6 kB

In fact, the total size of Very-very.net main page is 868.0 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. 30% of websites need less resources to load. Images take 349.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 51.3 kB

  • Original 64.3 kB
  • After minification 62.5 kB
  • After compression 13.0 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 51.3 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 17.0 kB

  • Original 349.6 kB
  • After minification 332.6 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. Very images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 205.0 kB

  • Original 279.4 kB
  • After minification 278.2 kB
  • After compression 74.4 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 205.0 kB or 73% of the original size.

CSS Optimization

-81%

Potential reduce by 142.1 kB

  • Original 174.6 kB
  • After minification 161.5 kB
  • After compression 32.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. Very-very.net needs all CSS files to be minified and compressed as it can save up to 142.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (33%)

Requests Now

70

After Optimization

47

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

Accessibility Review

very-very.net accessibility score

46

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

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

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

very-very.net best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

very-very.net SEO score

64

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Very-very.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Very-very.net 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 Very. 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: