Report Summary

  • 21

    Performance

    Renders faster than
    41% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 46

    Best Practices

    More advanced features
    available than in
    28% of websites

  • 76

    SEO

    Google-friendlier than
    44% of websites

tonya.co.jp

【珈琲問屋オンラインストア】100種類以上のコーヒー豆から選べる美味しい自家焙煎通販サイト(電話・FAX・メールでもご注文可能!)

Page Load Speed

1.2 sec in total

First Response

530 ms

Resources Loaded

539 ms

Page Rendered

83 ms

tonya.co.jp screenshot

About Website

Click here to check amazing Tonya content for Japan. Otherwise, check out these important facts you probably never knew about tonya.co.jp

珈琲問屋では、焼いていない生豆からお好みの焼き方や挽き方まで、あなただけのコーヒーを出荷の日に焙煎してお届けしています。100種類以上のコーヒー豆と6,000点を超える圧倒的な商品数、きっと、ここで最高の美味しい(おいしい)一杯がみつかるはず!

Visit tonya.co.jp

Key Findings

We analyzed Tonya.co.jp page load time and found that the first response time was 530 ms and then it took 622 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

tonya.co.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value15.6 s

1/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value33.8 s

0/100

10%

Network Requests Diagram

tonya.co.jp

530 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Tonya.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (530 ms) belongs to the original domain Tonya.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 417 B (46%)

Content Size

905 B

After Optimization

488 B

In fact, the total size of Tonya.co.jp main page is 905 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 905 B which makes up the majority of the site volume.

HTML Optimization

-46%

Potential reduce by 417 B

  • Original 905 B
  • After minification 903 B
  • After compression 488 B

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 417 B or 46% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

tonya.co.jp accessibility score

67

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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.

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

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tonya.co.jp best practices score

46

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

High

Registers an unload listener

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

tonya.co.jp SEO score

76

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8-JP;

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tonya.co.jp 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 Tonya.co.jp main page’s claimed encoding is utf-8-jp;. 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 Tonya. 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: