Tools & Wizards About Us
hantianblog.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% 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

  • 71

    SEO

    Google-friendlier than
    30% of websites

hantianblog.com

涵天食尚玩樂生活誌 - 美食分享、旅遊資訊、優惠住宿票券、懶人包整理

Page Load Speed

10 sec in total

First Response

1.4 sec

Resources Loaded

6.6 sec

Page Rendered

2 sec

hantianblog.com screenshot

About Website

Click here to check amazing Hantianblog content for Taiwan. Otherwise, check out these important facts you probably never knew about hantianblog.com

美食分享、旅遊資訊、優惠住宿票券、懶人包整理

Visit hantianblog.com

Key Findings

We analyzed Hantianblog.com page load time and found that the first response time was 1.4 sec and then it took 8.6 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

hantianblog.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value13,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.0 s

1/100

10%

Network Requests Diagram

hantianblog.com

1421 ms

wp-emoji-release.min.js

140 ms

css

23 ms

style.css

144 ms

style.css

146 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 15% of them (17 requests) were addressed to the original Hantianblog.com, 20% (23 requests) were made to Static.xx.fbcdn.net and 9% (10 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Hantianblog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 576.6 kB (35%)

Content Size

1.6 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hantianblog.com main page is 1.6 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 903.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 140.0 kB

  • Original 170.8 kB
  • After minification 164.8 kB
  • After compression 30.7 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 140.0 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 82.5 kB

  • Original 903.8 kB
  • After minification 821.3 kB

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

JavaScript Optimization

-61%

Potential reduce by 316.2 kB

  • Original 520.7 kB
  • After minification 504.4 kB
  • After compression 204.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 316.2 kB or 61% of the original size.

CSS Optimization

-86%

Potential reduce by 37.9 kB

  • Original 44.1 kB
  • After minification 32.3 kB
  • After compression 6.2 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. Hantianblog.com needs all CSS files to be minified and compressed as it can save up to 37.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 61 (58%)

Requests Now

106

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hantianblog.com

hantianblog.com

1421 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

140 ms

css

css

23 ms

style.css

style.css

144 ms

style.css

style.css

146 ms

jetpack.css

jetpack.css

146 ms

css3_red_glossy.css

css3_red_glossy.css

151 ms

jquery.js

jquery.js

286 ms

jquery-migrate.min.js

jquery-migrate.min.js

207 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

215 ms

tw-sack.min.js

tw-sack.min.js

217 ms

hantianblog.com

hantianblog.com

3589 ms

adsbygoogle.js

adsbygoogle.js

5 ms

show_ads.js

show_ads.js

60 ms

Agoda.SearchBoxV2.1.js

Agoda.SearchBoxV2.1.js

826 ms

devicepx-jetpack.js

devicepx-jetpack.js

56 ms

navigation.js

navigation.js

173 ms

e-201609.js

e-201609.js

5 ms

style.css

style.css

156 ms

960x189.jpg

960x189.jpg

329 ms

grey.gif

grey.gif

73 ms

like.php

like.php

186 ms

like.php

like.php

188 ms

like.php

like.php

133 ms

like.php

like.php

164 ms

like.php

like.php

138 ms

like.php

like.php

165 ms

like.php

like.php

179 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

92 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

85 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

83 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

123 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

112 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

115 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

108 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

103 ms

rU2ubZ6l1Q5.js

rU2ubZ6l1Q5.js

90 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

87 ms

rU2ubZ6l1Q5.js

rU2ubZ6l1Q5.js

82 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

73 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

66 ms

analytics.js

analytics.js

102 ms

20839835143_17befd3f88_o.png

20839835143_17befd3f88_o.png

387 ms

visitjapan_f36_170_170.jpg

visitjapan_f36_170_170.jpg

389 ms

201411pop.png

201411pop.png

640 ms

17147381746_7884b04f33_m.jpg

17147381746_7884b04f33_m.jpg

198 ms

142 ms

1920b11.jpg

1920b11.jpg

384 ms

960x189.jpg

960x189.jpg

720 ms

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

46 ms

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

110 ms

xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf

xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf

273 ms

PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf

PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf

224 ms

collect

collect

24 ms

ca-pub-7005786153452783.js

ca-pub-7005786153452783.js

195 ms

zrt_lookup.html

zrt_lookup.html

247 ms

show_ads_impl.js

show_ads_impl.js

73 ms

platform.js

platform.js

340 ms

likebox.php

likebox.php

272 ms

ads

ads

433 ms

osd.js

osd.js

59 ms

visitjapan_f36_170_170.jpg

visitjapan_f36_170_170.jpg

998 ms

jquery-ui-1.8.12.custom.min.js

jquery-ui-1.8.12.custom.min.js

72 ms

roNeOY-tz5Y.css

roNeOY-tz5Y.css

52 ms

UHhaxo8Cs3k.css

UHhaxo8Cs3k.css

46 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

56 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

53 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

52 ms

TTCre3391I0.js

TTCre3391I0.js

53 ms

js15.js

js15.js

201 ms

12342504_1062049260482086_5143010749590132184_n.jpg

12342504_1062049260482086_5143010749590132184_n.jpg

176 ms

10462756_789460824407599_1848049543099563628_n.jpg

10462756_789460824407599_1848049543099563628_n.jpg

138 ms

12341287_10205123824312354_8074873041958168210_n.jpg

12341287_10205123824312354_8074873041958168210_n.jpg

161 ms

190502_107604492653304_6779711_n.jpg

190502_107604492653304_6779711_n.jpg

163 ms

10372252_1603356239897122_7998386265575663588_n.jpg

10372252_1603356239897122_7998386265575663588_n.jpg

159 ms

10923631_839792099415745_901247234575356747_n.jpg

10923631_839792099415745_901247234575356747_n.jpg

162 ms

1383565_764905683556210_4358451346566269621_n.jpg

1383565_764905683556210_4358451346566269621_n.jpg

158 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

137 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

137 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

96 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

134 ms

page

page

434 ms

jquery-ui-1.8.12.custom.css

jquery-ui-1.8.12.custom.css

121 ms

loading_icon.gif

loading_icon.gif

68 ms

Default.aspx

Default.aspx

805 ms

Style3.css

Style3.css

551 ms

6845944991109138611

6845944991109138611

151 ms

abg.js

abg.js

156 ms

m_js_controller.js

m_js_controller.js

170 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

133 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

52 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

69 ms

postmessageRelay

postmessageRelay

68 ms

api.js

api.js

60 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

158 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

156 ms

s

s

49 ms

x_button_blue2.png

x_button_blue2.png

50 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

12 ms

rs=AGLTcCP3O_7Lv6wPM9DLZp_DouM8Z1J9hQ

rs=AGLTcCP3O_7Lv6wPM9DLZp_DouM8Z1J9hQ

12 ms

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

39 ms

rs=AGLTcCOR-Q-WA4NntzGWY98HeEAzJK-wTQ

rs=AGLTcCOR-Q-WA4NntzGWY98HeEAzJK-wTQ

75 ms

photo.jpg

photo.jpg

242 ms

IMG_9475-1.jpg

IMG_9475-1.jpg

242 ms

rs=AGLTcCOR-Q-WA4NntzGWY98HeEAzJK-wTQ

rs=AGLTcCOR-Q-WA4NntzGWY98HeEAzJK-wTQ

106 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

221 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

271 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

278 ms

2440337.php

2440337.php

77 ms

24821862279_db787ef873_o.jpg

24821862279_db787ef873_o.jpg

178 ms

rs=AGLTcCOR-Q-WA4NntzGWY98HeEAzJK-wTQ

rs=AGLTcCOR-Q-WA4NntzGWY98HeEAzJK-wTQ

82 ms

cc_605.js

cc_605.js

70 ms

all.js

all.js

96 ms

data.js

data.js

90 ms

g.gif

g.gif

44 ms

Accessibility Review

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

hantianblog.com SEO score

71

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

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

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hantianblog.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Hantianblog.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

hantianblog.com

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