Tools & Wizards About Us
yao800.co.jp screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

yao800.co.jp

やお九州 | 九州野菜と有機無農薬米を宅配する通販会社です。

Page Load Speed

13.6 sec in total

First Response

4.6 sec

Resources Loaded

8 sec

Page Rendered

1.1 sec

yao800.co.jp screenshot

About Website

Visit yao800.co.jp now to see the best up-to-date Yao 800 content for Japan and also check out these interesting facts you probably never knew about yao800.co.jp

やお九州 九州野菜と有機無農薬米を宅配します。安心安全の九州食品通販サイト

Visit yao800.co.jp

Key Findings

We analyzed Yao800.co.jp page load time and found that the first response time was 4.6 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

yao800.co.jp performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value32.3 s

0/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

yao800.co.jp

4559 ms

style.css

505 ms

jquery.min.js

6 ms

slide.js

347 ms

page_top.js

346 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 73% of them (40 requests) were addressed to the original Yao800.co.jp, 20% (11 requests) were made to Static.xx.fbcdn.net and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Yao800.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 176.0 kB (3%)

Content Size

6.0 MB

After Optimization

5.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yao800.co.jp main page is 6.0 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. 40% of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 7.5 kB

  • Original 11.6 kB
  • After minification 10.6 kB
  • After compression 4.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 7.5 kB or 65% of the original size.

Image Optimization

-3%

Potential reduce by 160.9 kB

  • Original 6.0 MB
  • After minification 5.8 MB

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. Yao 800 images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 1.5 kB

  • Original 35.1 kB
  • After minification 34.4 kB
  • After compression 33.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-76%

Potential reduce by 6.1 kB

  • Original 8.0 kB
  • After minification 5.8 kB
  • After compression 1.9 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. Yao800.co.jp needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yao800.co.jp

yao800.co.jp

4559 ms

style.css

style.css

505 ms

jquery.min.js

jquery.min.js

6 ms

slide.js

slide.js

347 ms

page_top.js

page_top.js

346 ms

page.php

page.php

353 ms

smart.png

smart.png

2819 ms

footbg.png

footbg.png

2206 ms

bg-beige.jpg

bg-beige.jpg

504 ms

hed-logo.png

hed-logo.png

353 ms

gnav-line.png

gnav-line.png

361 ms

gnav01.jpg

gnav01.jpg

711 ms

gnav02.jpg

gnav02.jpg

521 ms

gnav03.jpg

gnav03.jpg

704 ms

gnav04.jpg

gnav04.jpg

671 ms

btn-base.png

btn-base.png

694 ms

yao1.jpg

yao1.jpg

1494 ms

hatoyan.png

hatoyan.png

1709 ms

staff1.jpg

staff1.jpg

1386 ms

staff2.jpg

staff2.jpg

2632 ms

itn1.jpg

itn1.jpg

2408 ms

itn2.jpg

itn2.jpg

1827 ms

itn3.jpg

itn3.jpg

2219 ms

itn4.jpg

itn4.jpg

1995 ms

yahoo.png

yahoo.png

2165 ms

yaopack.png

yaopack.png

2499 ms

ranking1.jpg

ranking1.jpg

2547 ms

ranking2.jpg

ranking2.jpg

2729 ms

seisan.jpg

seisan.jpg

2921 ms

pro1.png

pro1.png

2668 ms

pro2.png

pro2.png

2721 ms

pro3.png

pro3.png

2812 ms

pro4.png

pro4.png

2838 ms

pro5.png

pro5.png

2894 ms

pro6.png

pro6.png

2903 ms

about1.jpg

about1.jpg

2992 ms

line.jpg

line.jpg

2994 ms

sns1.jpg

sns1.jpg

3008 ms

insta.png

insta.png

3066 ms

twitter.png

twitter.png

3075 ms

pagetop.png

pagetop.png

3093 ms

foot-logo.png

foot-logo.png

3169 ms

lFC1eVji7gN.css

lFC1eVji7gN.css

14 ms

DaPJf3IFK7Z.js

DaPJf3IFK7Z.js

22 ms

Y4zFOWmUObv.js

Y4zFOWmUObv.js

54 ms

xj_QemyOmNF.js

xj_QemyOmNF.js

55 ms

HbT8HXdZYIC.js

HbT8HXdZYIC.js

62 ms

kY8eYg-9-SS.js

kY8eYg-9-SS.js

55 ms

VFOmN3tQ-ee.js

VFOmN3tQ-ee.js

64 ms

p55HfXW__mM.js

p55HfXW__mM.js

60 ms

ALTQi95mOyD.js

ALTQi95mOyD.js

61 ms

292343998_420244530117042_6736382261363708495_n.jpg

292343998_420244530117042_6736382261363708495_n.jpg

297 ms

291945217_420244533450375_2811134688722597185_n.jpg

291945217_420244533450375_2811134688722597185_n.jpg

68 ms

ENoLOj8GKx_.js

ENoLOj8GKx_.js

7 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

4 ms

Accessibility Review

yao800.co.jp accessibility score

85

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

Best Practices

yao800.co.jp 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

yao800.co.jp SEO score

83

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

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

    N/A

  • Encoding

    UTF-8

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

yao800.co.jp

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