Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

Page Load Speed

2.8 sec in total

First Response

607 ms

Resources Loaded

2 sec

Page Rendered

180 ms

flower-drop.vivian.jp screenshot

About Website

Click here to check amazing Flower Drop Vivian content for Japan. Otherwise, check out these important facts you probably never knew about flower-drop.vivian.jp

Visit flower-drop.vivian.jp

Key Findings

We analyzed Flower-drop.vivian.jp page load time and found that the first response time was 607 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

flower-drop.vivian.jp performance score

99

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)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

flower-drop.vivian.jp

607 ms

style.css

180 ms

accnt.php

1260 ms

counter.png

792 ms

analyze.js

816 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 43% of them (3 requests) were addressed to the original Flower-drop.vivian.jp, 43% (3 requests) were made to Tofdrop.analytics.qlook.net and 14% (1 request) were made to Users595.lolipop.jp. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Users595.lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.6 kB (9%)

Content Size

64.4 kB

After Optimization

58.9 kB

In fact, the total size of Flower-drop.vivian.jp main page is 64.4 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. Images take 58.1 kB which makes up the majority of the site volume.

HTML Optimization

-49%

Potential reduce by 2.2 kB

  • Original 4.4 kB
  • After minification 4.4 kB
  • After compression 2.3 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 2.2 kB or 49% of the original size.

Image Optimization

-4%

Potential reduce by 2.2 kB

  • Original 58.1 kB
  • After minification 55.9 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 Drop Vivian images are well optimized though.

CSS Optimization

-65%

Potential reduce by 1.3 kB

  • Original 1.9 kB
  • After minification 1.7 kB
  • After compression 690 B

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-drop.vivian.jp needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 65% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

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

Accessibility Review

flower-drop.vivian.jp accessibility score

68

Accessibility Issues

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

Best Practices

flower-drop.vivian.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

flower-drop.vivian.jp SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flower-drop.vivian.jp 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 Flower-drop.vivian.jp 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

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