Tools & Wizards About Us
2hongo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

2hongo.com

2hongo - Japanese Dictionary with Context | 2hongo

Page Load Speed

12.3 sec in total

First Response

4.6 sec

Resources Loaded

7.4 sec

Page Rendered

278 ms

2hongo.com screenshot

About Website

Visit 2hongo.com now to see the best up-to-date 2 Hongo content and also check out these interesting facts you probably never knew about 2hongo.com

Comprehensive Japanese dictionary with word relationships, grammar patterns, and context. Built for serious learners.

Visit 2hongo.com

Key Findings

We analyzed 2hongo.com page load time and found that the first response time was 4.6 sec and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize 2hongo.com rating and web reputation

Performance Metrics

2hongo.com performance score

0

Network Requests Diagram

2hongo.com

4615 ms

style.css

308 ms

sociable.css

343 ms

tw-sack.min.js

244 ms

wp-embed.min.js

334 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 42% of them (31 requests) were addressed to the original 2hongo.com, 16% (12 requests) were made to Maps.googleapis.com and 14% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain 2hongo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 554.9 kB (49%)

Content Size

1.1 MB

After Optimization

584.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 2hongo.com main page is 1.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. 50% of websites need less resources to load. Javascripts take 722.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 19.0 kB

  • Original 24.3 kB
  • After minification 23.4 kB
  • After compression 5.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. 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 19.0 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 7.3 kB

  • Original 365.6 kB
  • After minification 358.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. 2 Hongo images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 506.1 kB

  • Original 722.7 kB
  • After minification 722.6 kB
  • After compression 216.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 506.1 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 22.5 kB

  • Original 26.3 kB
  • After minification 16.7 kB
  • After compression 3.8 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. 2hongo.com needs all CSS files to be minified and compressed as it can save up to 22.5 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

65

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2hongo.com

2hongo.com

4615 ms

style.css

style.css

308 ms

sociable.css

sociable.css

343 ms

tw-sack.min.js

tw-sack.min.js

244 ms

wp-embed.min.js

wp-embed.min.js

334 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

162 ms

maps

maps

65 ms

clip_16_16_w.gif

clip_16_16_w.gif

485 ms

ybm16.gif

ybm16.gif

569 ms

add_icon_mini_01.gif

add_icon_mini_01.gif

342 ms

newsingit_s.gif

newsingit_s.gif

569 ms

internal.png

internal.png

89 ms

title-yono.gif

title-yono.gif

494 ms

topyono.gif

topyono.gif

1425 ms

printfriendly.png

printfriendly.png

318 ms

digg.png

digg.png

311 ms

stumbleupon.png

stumbleupon.png

320 ms

delicious.png

delicious.png

319 ms

facebook.png

facebook.png

468 ms

yahoobuzz.png

yahoobuzz.png

474 ms

twitter.png

twitter.png

477 ms

googlebookmark.png

googlebookmark.png

476 ms

b_entry.gif

b_entry.gif

632 ms

twitter.gif

twitter.gif

631 ms

tumblr.gif

tumblr.gif

635 ms

google.gif

google.gif

642 ms

16x16-digg-guy.gif

16x16-digg-guy.gif

655 ms

bg_body.jpg

bg_body.jpg

780 ms

body_bg-twt.gif

body_bg-twt.gif

781 ms

bg_header.jpg

bg_header.jpg

785 ms

arrow01.gif

arrow01.gif

793 ms

bg_midashi1.jpg

bg_midashi1.jpg

811 ms

border_dot.gif

border_dot.gif

1691 ms

arrow03.gif

arrow03.gif

937 ms

btn_pagetop.gif

btn_pagetop.gif

956 ms

arrow05.gif

arrow05.gif

953 ms

rss.gif

rss.gif

967 ms

embed

embed

1730 ms

blog.friendfeed.com

blog.friendfeed.com

112 ms

js

js

86 ms

init_embed.js

init_embed.js

78 ms

common.js

common.js

71 ms

map.js

map.js

71 ms

google4.png

google4.png

171 ms

overlay.js

overlay.js

19 ms

util.js

util.js

172 ms

onion.js

onion.js

119 ms

search_impl.js

search_impl.js

163 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

575 ms

stats.js

stats.js

169 ms

openhand_8_8.cur

openhand_8_8.cur

102 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

102 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

92 ms

kh

kh

131 ms

kh

kh

207 ms

transparent.png

transparent.png

83 ms

controls.js

controls.js

27 ms

css

css

110 ms

entity11.png

entity11.png

74 ms

vt

vt

188 ms

vt

vt

178 ms

vt

vt

212 ms

vt

vt

156 ms

vt

vt

210 ms

vt

vt

140 ms

vt

vt

232 ms

vt

vt

253 ms

vt

vt

254 ms

mapcnt6.png

mapcnt6.png

38 ms

tmapctrl.png

tmapctrl.png

36 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

45 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

63 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

82 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

101 ms

SEO Factors

2hongo.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2hongo.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 2hongo.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

2hongo.com

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