Tools & Wizards About Us
hojotea.com screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

hojotea.com

中国・台湾・日本茶販売[高級茶葉・和製手作り茶器専門店HOJO]中国茶等を販売・卸販売

Page Load Speed

7.5 sec in total

First Response

921 ms

Resources Loaded

5.9 sec

Page Rendered

685 ms

hojotea.com screenshot

About Website

Click here to check amazing Hojotea content for United States. Otherwise, check out these important facts you probably never knew about hojotea.com

中国茶販売、専門家によるこだわりの烏龍茶・台湾茶・高級紅茶・ジャスミン茶の無農薬・有機栽培高級茶を通販（通信販売）・卸販売している専門店です。中国茶の詳細情報を掲載。

Visit hojotea.com

Key Findings

We analyzed Hojotea.com page load time and found that the first response time was 921 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

hojotea.com performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.4 s

99/100

10%

Network Requests Diagram

hojotea.com

921 ms

style.css

711 ms

urchin.js

17 ms

ga.js

33 ms

sho_m03.jpg

1500 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 35% of them (28 requests) were addressed to the original Hojotea.com, 25% (20 requests) were made to Static.xx.fbcdn.net and 19% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Hojotea.com.

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hojotea.com main page is 1.4 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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 43.1 kB

  • Original 56.1 kB
  • After minification 53.2 kB
  • After compression 13.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 43.1 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 41.6 kB

  • Original 1.3 MB
  • After minification 1.2 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. Hojotea images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 1.0 kB

  • Original 24.0 kB
  • After minification 24.0 kB
  • After compression 23.0 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

-86%

Potential reduce by 46.8 kB

  • Original 54.1 kB
  • After minification 41.9 kB
  • After compression 7.3 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. Hojotea.com needs all CSS files to be minified and compressed as it can save up to 46.8 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

77

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hojotea.com

hojotea.com

921 ms

style.css

style.css

711 ms

urchin.js

urchin.js

17 ms

ga.js

ga.js

33 ms

sho_m03.jpg

sho_m03.jpg

1500 ms

ssl_key.gif

ssl_key.gif

794 ms

logo020.gif

logo020.gif

359 ms

5000yen_banner.gif

5000yen_banner.gif

361 ms

bn_fax.jpg

bn_fax.jpg

361 ms

flg_eng2.gif

flg_eng2.gif

374 ms

profile_banner01.gif

profile_banner01.gif

384 ms

mag_logo1.gif

mag_logo1.gif

385 ms

kyusu_banner04.jpg

kyusu_banner04.jpg

719 ms

topbanner_005.jpg

topbanner_005.jpg

923 ms

topbanner_004.jpg

topbanner_004.jpg

928 ms

top_policy01.jpg

top_policy01.jpg

1328 ms

topbanner_001.jpg

topbanner_001.jpg

1121 ms

topbanner_002.jpg

topbanner_002.jpg

1160 ms

topbanner_003.jpg

topbanner_003.jpg

2016 ms

bn_safe01.jpg

bn_safe01.jpg

1447 ms

can_04.jpg

can_04.jpg

1297 ms

card-logo_02.gif

card-logo_02.gif

1510 ms

shop02.gif

shop02.gif

1533 ms

saeko09.jpg

saeko09.jpg

1826 ms

akira09.jpg

akira09.jpg

1869 ms

bn_addtel05.gif

bn_addtel05.gif

1804 ms

pho150_s01.jpg

pho150_s01.jpg

1884 ms

o06_01.jpg

o06_01.jpg

2407 ms

d14_022.jpg

d14_022.jpg

2925 ms

w04_07.jpg

w04_07.jpg

2735 ms

g25_17.jpg

g25_17.jpg

2582 ms

all.js

all.js

159 ms

__utm.gif

__utm.gif

17 ms

__utm.gif

__utm.gif

50 ms

collect

collect

58 ms

472 ms

xd_arbiter.php

xd_arbiter.php

156 ms

xd_arbiter.php

xd_arbiter.php

275 ms

xd_arbiter.php

xd_arbiter.php

83 ms

like_box.php

like_box.php

449 ms

9hoskrDulPm.css

9hoskrDulPm.css

179 ms

MrxxdBM8xso.css

MrxxdBM8xso.css

219 ms

YLIWaFzOgE1.css

YLIWaFzOgE1.css

287 ms

CsWUh2Zrtn2.css

CsWUh2Zrtn2.css

324 ms

8pOzSEmwQUd.css

8pOzSEmwQUd.css

333 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

347 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

377 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

297 ms

TTCre3391I0.js

TTCre3391I0.js

344 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

364 ms

b_6HNn_J2BZ.js

b_6HNn_J2BZ.js

364 ms

7cm7D75Y0Sf.js

7cm7D75Y0Sf.js

398 ms

rFmE1g6Dkoz.js

rFmE1g6Dkoz.js

483 ms

336JejShbZp.js

336JejShbZp.js

395 ms

421719_231093953654367_832968578_n.jpg

421719_231093953654367_832968578_n.jpg

322 ms

safe_image.php

safe_image.php

269 ms

safe_image.php

safe_image.php

364 ms

safe_image.php

safe_image.php

401 ms

safe_image.php

safe_image.php

447 ms

423335_230839493679813_2108135582_n.jpg

423335_230839493679813_2108135582_n.jpg

346 ms

598437_181749138631708_481248134_n.jpg

598437_181749138631708_481248134_n.jpg

426 ms

422824_324529100917202_161411299_n.jpg

422824_324529100917202_161411299_n.jpg

450 ms

10444342_912845835434142_5303921552359791440_n.jpg

10444342_912845835434142_5303921552359791440_n.jpg

427 ms

12063845_915170951934698_4078206279195621919_n.jpg

12063845_915170951934698_4078206279195621919_n.jpg

426 ms

11025166_872740726130759_3509397253515389096_n.jpg

11025166_872740726130759_3509397253515389096_n.jpg

428 ms

12642698_963907113690990_508113785718840859_n.jpg

12642698_963907113690990_508113785718840859_n.jpg

429 ms

12246906_817891911667712_495311197744940900_n.jpg

12246906_817891911667712_495311197744940900_n.jpg

464 ms

1503428_1523051964613568_9113451590315437690_n.jpg

1503428_1523051964613568_9113451590315437690_n.jpg

465 ms

297279_188929934511420_1103096215_n.jpg

297279_188929934511420_1103096215_n.jpg

465 ms

12122954_462998817216778_6490500834356065021_n.jpg

12122954_462998817216778_6490500834356065021_n.jpg

468 ms

10359246_461288704067993_4232713042273518233_n.jpg

10359246_461288704067993_4232713042273518233_n.jpg

466 ms

11047913_10205142042330358_4668912755022800818_n.jpg

11047913_10205142042330358_4668912755022800818_n.jpg

485 ms

12391045_479644235541075_2185436992477127989_n.jpg

12391045_479644235541075_2185436992477127989_n.jpg

499 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

59 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

57 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

58 ms

a-ZN6WoEOje.png

a-ZN6WoEOje.png

58 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

41 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

75 ms

Accessibility Review

hojotea.com accessibility score

67

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

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

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

Best Practices

hojotea.com best practices score

75

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

hojotea.com SEO score

75

Search Engine Optimization Advices

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 Hojotea.com 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 Hojotea.com 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

hojotea.com

Open Graph data is detected on the main page of Hojotea. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: