Tools & Wizards About Us
tea4two.jp screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

tea4two.jp

ファミコン 通販 TEA4TWO / TOPページ

Page Load Speed

9.1 sec in total

First Response

627 ms

Resources Loaded

7.4 sec

Page Rendered

1.1 sec

tea4two.jp screenshot

About Website

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

ファミコン通販 ファミコン、スーパーファミコン、ディスクシステム、PCエンジン、ゲームボーイ、レトロゲーム専門店。【ファミコン 通販 TEA4TWO】

Visit tea4two.jp

Key Findings

We analyzed Tea4two.jp page load time and found that the first response time was 627 ms and then it took 8.5 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

tea4two.jp performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.338

33/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

tea4two.jp

627 ms

tea4two.jp

4189 ms

all.css

28 ms

style.css

1358 ms

front.bundle.js

1398 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 79% of them (34 requests) were addressed to the original Tea4two.jp, 14% (6 requests) were made to Kamogawa.mag2.com and 7% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Tea4two.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.5 kB (5%)

Content Size

5.2 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-94%

Potential reduce by 185.3 kB

  • Original 196.2 kB
  • After minification 78.1 kB
  • After compression 10.8 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. This page needs HTML code to be minified as it can gain 118.1 kB, which is 60% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 185.3 kB or 94% of the original size.

Image Optimization

-0%

Potential reduce by 5.6 kB

  • Original 4.9 MB
  • After minification 4.9 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. TEA4TWO images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 16.2 kB

  • Original 87.7 kB
  • After minification 87.7 kB
  • After compression 71.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 16.2 kB or 18% of the original size.

CSS Optimization

-41%

Potential reduce by 42.3 kB

  • Original 103.9 kB
  • After minification 103.9 kB
  • After compression 61.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. Tea4two.jp needs all CSS files to be minified and compressed as it can save up to 42.3 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (26%)

Requests Now

34

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TEA4TWO. 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

tea4two.jp

tea4two.jp

627 ms

tea4two.jp

tea4two.jp

4189 ms

all.css

all.css

28 ms

style.css

style.css

1358 ms

front.bundle.js

front.bundle.js

1398 ms

customize.css

customize.css

526 ms

function.js

function.js

177 ms

eccube.js

eccube.js

182 ms

customize.js

customize.js

352 ms

logo_white.svg

logo_white.svg

179 ms

loupe.png

loupe.png

170 ms

logo_blue.svg

logo_blue.svg

176 ms

grid.png

grid.png

187 ms

lens.png

lens.png

182 ms

help.png

help.png

1184 ms

user.png

user.png

348 ms

arrow.png

arrow.png

353 ms

email.png

email.png

360 ms

top_slider_pc01.jpg

top_slider_pc01.jpg

1548 ms

top_slider_sp01.jpg

top_slider_sp01.jpg

723 ms

top_slider_pc02.jpg

top_slider_pc02.jpg

689 ms

top_slider_sp02.jpg

top_slider_sp02.jpg

1226 ms

top_slider_pc03.jpg

top_slider_pc03.jpg

1060 ms

top_slider_sp03.jpg

top_slider_sp03.jpg

865 ms

mark_dendo.gif

mark_dendo.gif

899 ms

logo_mini.gif

logo_mini.gif

1035 ms

unpaid_banner.gif

unpaid_banner.gif

1074 ms

ITEM-TABBATx1.jpg

ITEM-TABBATx1.jpg

1204 ms

ITEM-FC-DSK-BELT_1.JPG

ITEM-FC-DSK-BELT_1.JPG

1236 ms

ITEM-AN-505B.JPG

ITEM-AN-505B.JPG

1249 ms

ITEM-FC-HW-DISK.JPG

ITEM-FC-HW-DISK.JPG

1705 ms

ITEM-HW-SFC.jpg

ITEM-HW-SFC.jpg

1376 ms

ITEM-FC-KAV-VAL_1.jpg

ITEM-FC-KAV-VAL_1.jpg

1402 ms

ITEM-FC-KAV_1.jpg

ITEM-FC-KAV_1.jpg

1412 ms

ITEM-FCPW-WDCAMP3D.JPG

ITEM-FCPW-WDCAMP3D.JPG

1426 ms

fa-solid-900.woff

fa-solid-900.woff

48 ms

fa-regular-400.woff

fa-regular-400.woff

48 ms

small_o_left_top.gif

small_o_left_top.gif

599 ms

small_o_right_top.gif

small_o_right_top.gif

611 ms

small_o_tit.gif

small_o_tit.gif

611 ms

small_o_bg.gif

small_o_bg.gif

795 ms

small_o_left_bot.gif

small_o_left_bot.gif

657 ms

small_o_right_bot.gif

small_o_right_bot.gif

658 ms

Accessibility Review

tea4two.jp accessibility score

89

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

tea4two.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tea4two.jp SEO score

91

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

tea4two.jp

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