Tools & Wizards About Us
hooriza.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hooriza.com

블로그를 후리자 :: iOS 에서 쓸만한 오프라인 구글지도 찾기

Page Load Speed

16.2 sec in total

First Response

1.9 sec

Resources Loaded

13.8 sec

Page Rendered

476 ms

hooriza.com screenshot

About Website

Click here to check amazing Hooriza content for South Korea. Otherwise, check out these important facts you probably never knew about hooriza.com

Visit hooriza.com

Key Findings

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

Performance Metrics

hooriza.com performance score

0

Network Requests Diagram

hooriza.com

1865 ms

jquery.js

525 ms

hbase.js

537 ms

style.css

543 ms

career.css

546 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 93% of them (50 requests) were addressed to the original Hooriza.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (9.3 sec) belongs to the original domain Hooriza.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 374.9 kB (69%)

Content Size

541.5 kB

After Optimization

166.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hooriza.com main page is 541.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. HTML takes 308.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 230.3 kB

  • Original 308.3 kB
  • After minification 290.5 kB
  • After compression 78.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 230.3 kB or 75% of the original size.

Image Optimization

-17%

Potential reduce by 5.5 kB

  • Original 32.4 kB
  • After minification 26.9 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. Obviously, Hooriza needs image optimization as it can save up to 5.5 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 120.3 kB

  • Original 175.9 kB
  • After minification 154.7 kB
  • After compression 55.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 120.3 kB or 68% of the original size.

CSS Optimization

-76%

Potential reduce by 18.8 kB

  • Original 24.9 kB
  • After minification 19.1 kB
  • After compression 6.0 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. Hooriza.com needs all CSS files to be minified and compressed as it can save up to 18.8 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (77%)

Requests Now

52

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hooriza. 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 from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hooriza.com

hooriza.com

1865 ms

jquery.js

jquery.js

525 ms

hbase.js

hbase.js

537 ms

style.css

style.css

543 ms

career.css

career.css

546 ms

pinyin.css

pinyin.css

542 ms

include.js

include.js

1058 ms

pinyin.js

pinyin.js

1067 ms

flash.js

flash.js

1084 ms

script.js

script.js

1085 ms

gesture.js

gesture.js

1085 ms

CFInstall.min.js

CFInstall.min.js

351 ms

geshi_base.css

geshi_base.css

1357 ms

geshi_light.css

geshi_light.css

1582 ms

lt_main.js

lt_main.js

1613 ms

lgn_main.js

lgn_main.js

1618 ms

style.css

style.css

1622 ms

style.css

style.css

1621 ms

sr_main.js

sr_main.js

1907 ms

style.css

style.css

2108 ms

EAF4.js

EAF4.js

2147 ms

common2.js

common2.js

2141 ms

gallery.js

gallery.js

2152 ms

traffic.php

traffic.php

2287 ms

hooriza

hooriza

126 ms

1350477812.gif

1350477812.gif

480 ms

me2day.gif

me2day.gif

478 ms

twitter.gif

twitter.gif

502 ms

search-btn.png

search-btn.png

503 ms

btn_rss.png

btn_rss.png

520 ms

tab_top.gif

tab_top.gif

654 ms

tab_closed.gif

tab_closed.gif

987 ms

navi_back_active.gif

navi_back_active.gif

988 ms

tab_treed.gif

tab_treed.gif

1011 ms

tab_treed_end.gif

tab_treed_end.gif

1013 ms

tab_isleaf.gif

tab_isleaf.gif

1036 ms

count.php

count.php

1204 ms

textcube.jpg

textcube.jpg

1771 ms

cgv.php

cgv.php

1507 ms

topmenu.gif

topmenu.gif

1470 ms

roundlt.gif

roundlt.gif

1476 ms

roundtop.gif

roundtop.gif

1487 ms

roundgt.gif

roundgt.gif

1676 ms

bg_footer.gif

bg_footer.gif

1977 ms

bul.gif

bul.gif

1856 ms

bg.png

bg.png

1780 ms

fg.png

fg.png

1793 ms

navi_back_noactive.gif

navi_back_noactive.gif

1942 ms

navi_back_noactive_end.gif

navi_back_noactive_end.gif

1993 ms

analytics.js

analytics.js

58 ms

feeder

feeder

9259 ms

collect

collect

17 ms

style.mobile.css

style.mobile.css

487 ms

style.print.css

style.print.css

464 ms

SEO Factors

hooriza.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hooriza.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Hooriza.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

hooriza.com

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