Tools & Wizards About Us
maiko.ne.jp screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

maiko.ne.jp

京都 こだわりの玉露・宇治抹茶の取扱い｜舞妓の茶本舗

Page Load Speed

9.1 sec in total

First Response

793 ms

Resources Loaded

6.9 sec

Page Rendered

1.4 sec

maiko.ne.jp screenshot

About Website

Visit maiko.ne.jp now to see the best up-to-date Maiko content for Germany and also check out these interesting facts you probably never knew about maiko.ne.jp

玉露や抹茶、かりがね茶、煎茶、緑茶、ほうじ茶、玄米茶など様々な日本茶の通販・お取り寄せなら京都の老舗の舞妓の茶本舗。お中元やお歳暮などのギフトにも最適な商品が勢ぞろい。

Visit maiko.ne.jp

Key Findings

We analyzed Maiko.ne.jp page load time and found that the first response time was 793 ms and then it took 8.3 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

maiko.ne.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.351

31/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

maiko.ne.jp

793 ms

pcsmpflg.js

353 ms

addfriends_ja.png

598 ms

re-maiko1.jpg

249 ms

topbanner1.jpg

912 ms

Our browser made a total of 141 requests to load all elements on the main page. We found that 90% of them (127 requests) were addressed to the original Maiko.ne.jp, 3% (4 requests) were made to Youtube.com and 2% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Maiko.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 437.9 kB (21%)

Content Size

2.1 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 92.3 kB

  • Original 108.5 kB
  • After minification 87.2 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 21.3 kB, which is 20% 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 92.3 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

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

JavaScript Optimization

-60%

Potential reduce by 141.7 kB

  • Original 234.8 kB
  • After minification 232.9 kB
  • After compression 93.1 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 141.7 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 202.6 kB

  • Original 244.2 kB
  • After minification 244.1 kB
  • After compression 41.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. Maiko.ne.jp needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

138

After Optimization

102

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

maiko.ne.jp

maiko.ne.jp

793 ms

pcsmpflg.js

pcsmpflg.js

353 ms

addfriends_ja.png

addfriends_ja.png

598 ms

re-maiko1.jpg

re-maiko1.jpg

249 ms

topbanner1.jpg

topbanner1.jpg

912 ms

topbanner2.jpg

topbanner2.jpg

401 ms

top-boutique.jpg

top-boutique.jpg

600 ms

topbanner3.jpg

topbanner3.jpg

548 ms

topbanner4.jpg

topbanner4.jpg

401 ms

top11.jpg

top11.jpg

579 ms

topbanner5.jpg

topbanner5.jpg

600 ms

topbanner6.jpg

topbanner6.jpg

598 ms

banner-ma.gif

banner-ma.gif

608 ms

banner-in.gif

banner-in.gif

714 ms

banner-qu.gif

banner-qu.gif

790 ms

banner-sh.gif

banner-sh.gif

763 ms

banner-gu.gif

banner-gu.gif

773 ms

banner-ca.gif

banner-ca.gif

820 ms

jpn.gif

jpn.gif

853 ms

eng.gif

eng.gif

952 ms

ger.gif

ger.gif

960 ms

rus.gif

rus.gif

979 ms

chinese.gif

chinese.gif

1015 ms

thanks1.jpg

thanks1.jpg

1236 ms

award.jpg

award.jpg

1101 ms

kingdom.jpg

kingdom.jpg

1299 ms

yamashita.jpg

yamashita.jpg

1308 ms

kyo4.jpg

kyo4.jpg

1348 ms

yucha4.jpg

yucha4.jpg

1563 ms

banner.jpg

banner.jpg

1290 ms

banner.jpg

banner.jpg

1446 ms

groll6.jpg

groll6.jpg

1559 ms

fin-b.jpg

fin-b.jpg

1506 ms

banner-pu.jpg

banner-pu.jpg

1523 ms

mark1.gif

mark1.gif

1601 ms

charge.jpg

charge.jpg

1651 ms

rakuten2.jpg

rakuten2.jpg

1711 ms

fb.gif

fb.gif

1697 ms

FFYaP_ANrYw

FFYaP_ANrYw

122 ms

HdvsJJ-GLUk

HdvsJJ-GLUk

123 ms

2Q6ZtsFTlg0

2Q6ZtsFTlg0

109 ms

pGaSfLfXsBY

pGaSfLfXsBY

118 ms

ga.js

ga.js

33 ms

boss.jpg

boss.jpg

1622 ms

__utm.gif

__utm.gif

48 ms

bn.gif

bn.gif

1576 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

29 ms

www-embed-player.js

www-embed-player.js

53 ms

base.js

base.js

110 ms

2016-1.jpg

2016-1.jpg

1811 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

112 ms

ad_status.js

ad_status.js

101 ms

yamashita.jpg

yamashita.jpg

1316 ms

award1.jpg

award1.jpg

1684 ms

kingdom1.jpg

kingdom1.jpg

1761 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

127 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

121 ms

lineup.gif

lineup.gif

1420 ms

5018-1.jpg

5018-1.jpg

1443 ms

ss-banner2.jpg

ss-banner2.jpg

1477 ms

gyokuro.jpg

gyokuro.jpg

1617 ms

sencha.jpg

sencha.jpg

1532 ms

karigane.jpg

karigane.jpg

1519 ms

maccha.jpg

maccha.jpg

1659 ms

organic3.jpg

organic3.jpg

1688 ms

ryo1-mini.jpg

ryo1-mini.jpg

1649 ms

asairi5.jpg

asairi5.jpg

1627 ms

houji.jpg

houji.jpg

1594 ms

genmai.jpg

genmai.jpg

1577 ms

happiness-b.jpg

happiness-b.jpg

1676 ms

bancha.jpg

bancha.jpg

1696 ms

tea.jpg

tea.jpg

1661 ms

summer1-mini.jpg

summer1-mini.jpg

1563 ms

pure.jpg

pure.jpg

1450 ms

beni2.jpg

beni2.jpg

1431 ms

gift.jpg

gift.jpg

1550 ms

gb50-4-mini.jpg

gb50-4-mini.jpg

1546 ms

henrei.jpg

henrei.jpg

1517 ms

choco1.jpg

choco1.jpg

1426 ms

choco.jpg

choco.jpg

1373 ms

jam6.jpg

jam6.jpg

1382 ms

groll7.jpg

groll7.jpg

1530 ms

fin.jpg

fin.jpg

1505 ms

confeito.jpg

confeito.jpg

1466 ms

cookie6.jpg

cookie6.jpg

1420 ms

kashi.jpg

kashi.jpg

1389 ms

kobu.jpg

kobu.jpg

1387 ms

kayu.jpg

kayu.jpg

1553 ms

mini.jpg

mini.jpg

1521 ms

yucha5.jpg

yucha5.jpg

1431 ms

gyokuro2.jpg

gyokuro2.jpg

1323 ms

sencha2.jpg

sencha2.jpg

1301 ms

banner1.jpg

banner1.jpg

1249 ms

banner2.jpg

banner2.jpg

1288 ms

back2.gif

back2.gif

1303 ms

lineup1.gif

lineup1.gif

1328 ms

gift-image.jpg

gift-image.jpg

1311 ms

yamashita1.jpg

yamashita1.jpg

1276 ms

fin1.jpg

fin1.jpg

1231 ms

confeito1.jpg

confeito1.jpg

1265 ms

info.gif

info.gif

1244 ms

amakara.jpg

amakara.jpg

1289 ms

award2015.jpg

award2015.jpg

1285 ms

215011.jpg

215011.jpg

1258 ms

201509fin1.jpg

201509fin1.jpg

1240 ms

mirano.jpg

mirano.jpg

1471 ms

top-ochatsumi.jpg

top-ochatsumi.jpg

1455 ms

shincha.jpg

shincha.jpg

2659 ms

udo.jpg

udo.jpg

1466 ms

hisho.jpg

hisho.jpg

1482 ms

aji.jpg

aji.jpg

1240 ms

book4.jpg

book4.jpg

1313 ms

water9.jpg

water9.jpg

1552 ms

tabemono.jpg

tabemono.jpg

1486 ms

josei.jpg

josei.jpg

1524 ms

chicago.jpg

chicago.jpg

1480 ms

ichida.jpg

ichida.jpg

1472 ms

kyu.jpg

kyu.jpg

1473 ms

tokudane.jpg

tokudane.jpg

1501 ms

ba.jpg

ba.jpg

1511 ms

sugiru.jpg

sugiru.jpg

1514 ms

rakuten.jpg

rakuten.jpg

1516 ms

boutique4.jpg

boutique4.jpg

1616 ms

banner.jpg

banner.jpg

1491 ms

chaco1.gif

chaco1.gif

1458 ms

maiko.gif

maiko.gif

1476 ms

colopl.jpg

colopl.jpg

1476 ms

maiko1.gif

maiko1.gif

1558 ms

banner-jp1.gif

banner-jp1.gif

202 ms

banner-en1.gif

banner-en1.gif

204 ms

banner-ma1.gif

banner-ma1.gif

364 ms

banner-in1.gif

banner-in1.gif

207 ms

banner-qu1.gif

banner-qu1.gif

186 ms

banner-sh1.gif

banner-sh1.gif

194 ms

banner-gu1.gif

banner-gu1.gif

366 ms

banner-ca1.gif

banner-ca1.gif

383 ms

banner-co1.gif

banner-co1.gif

409 ms

banner-ac1.gif

banner-ac1.gif

383 ms

banner-ko1.gif

banner-ko1.gif

398 ms

banner-ns1.gif

banner-ns1.gif

568 ms

banner-ge1.gif

banner-ge1.gif

564 ms

Accessibility Review

maiko.ne.jp accessibility score

88

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.

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

Best Practices

maiko.ne.jp best practices score

75

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

SEO Factors

maiko.ne.jp SEO score

96

Search Engine Optimization Advices

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

    N/A

  • Encoding

    SHIFT_JIS

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

maiko.ne.jp

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