Analyze

aforz.biz: 総合検索エンジンひらめき情報STREET

ディレクトリ型総合検索エンジンひらめき情報STREETはアクセス向上に欠かせないHTML形式の検索エンジンです

Page load speed analysis

  • 48/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    771 ms

  • Resources loaded

    4 sec

  • Page rendered

    1.3 sec

  • Total page load time

    6.1 sec

Click here to check amazing Aforz content for Japan. Otherwise, check out these important facts you probably never knew about aforz.biz

We analyzed Aforz.biz page load time and found that the first response time was 771 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Page optimization

  • HTML 26.3 kB
    Images 183.3 kB
    Javascripts 159.4 kB
    CSS 13.2 kB

    In fact, the total size of Aforz.biz main page is 382.3 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. 40% of websites need less resources to load. Images take 183.3 kB which makes up the majority of the site volume.

    • Original 26.3 kB
    • After minification 23.7 kB
    • After compression 7.0 kB

    HTML optimization

    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.3 kB or 73% of the original size.

    • Original 183.3 kB
    • After optimization 164.0 kB

    Image optimization

    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, Aforz needs image optimization as it can save up to 19.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

    • Original 159.4 kB
    • After minification 148.2 kB
    • After compression 49.6 kB

    JavaScript optimization

    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 109.9 kB or 69% of the original size.

    • Original 13.2 kB
    • After minification 8.8 kB
    • After compression 2.5 kB

    CSS optimization

    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. Aforz.biz needs all CSS files to be minified and compressed as it can save up to 10.7 kB or 81% of the original size.

Network requests diagram

  • aforz.biz
  • style.css
  • title_logo.gif
  • main_img800_100.jpg
  • normal_468x60.jpg
  • show
  • folder.gif
  • index.html
  • rankf.php
  • aforz.js
  • rranking.gif
  • smerankcheck.php
  • bg.gif
  • topmenu_bg.gif
  • topmenu_line.gif
  • h2_bg.gif
  • total_cnt.cgi
  • temp_cnt.cgi
  • count.cgi
  • count.cgi
  • count.cgi
  • www.fzzb.net
  • pvi.php
  • top_mr.html
  • top_bana.html
  • midashi_bg1.gif
  • bottom_img800_55.jpg
  • ac.css
  • linkbanner_pink.gif
  • bc_88x31.php
  • adref4.png
  • tekichen.gif
  • com.css
  • acctag.js
  • show_ads.js
  • rakuten_widget.js
  • fzzb.js
  • rank.php
  • acclog.cgi
  • kabe03.gif
  • top-img.jpg
  • menu02.gif
  • 001.gif
  • 002.gif
  • 003.gif
  • 004.gif
  • 005.gif
  • 006.gif
  • 007.gif
  • mail-y.gif
  • rranking.gif
  • ca-pub-6045562568209275.js
  • zrt_lookup.html
  • show_ads_impl.js
  • action.html
  • action.gif
  • ads
  • osd.js
  • ads
  • ads
  • abg.js
  • 15122106571364463425
  • s
  • m_js_controller.js
  • googlelogo_color_112x36dp.png
  • x_button_blue2.png
  • fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
  • 88x31.gif
  • mtwidget04.affiliate.rakuten.co.jp
  • kabe11.jpg
  • data06.gif
  • ads
  • sougomatome.gif
  • mtwidget04.affiliate.rakuten.co.jp
  • ads
  • special-b.gif
  • lin05.gif
  • icon10.gif
  • gensen-bs.gif
  • lin07.gif
  • pvi.php
  • pvi.php
  • toplink-s.gif
  • js
  • favicon
  • nessie_icon_tiamat_white.png
  • css
  • googlelogo_dark_color_84x28dp.png
  • css
  • iconx2-000000.png
  • googlelogo_dark_color_84x28dp.png
  • zN7GBFwfMP4uA6AR0HCoLQ.ttf
  • futback04.gif
  • img
  • ck-confirm
  • pixel
  • Q116_Wu_Com_Awareness_V3_D_468x60_EN_US.jpg
  • lidar.js
  • sbhK2lTE.js
  • cTrvNaRi.html
  • activeview

Our browser made a total of 103 requests to load all elements on the main page. We found that 22% of them (23 requests) were addressed to the original Aforz.biz, 26% (27 requests) were made to Fzzb.net and 8% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Dl.kasperskylabs.jp.

Additional info on aforz.biz

Requests

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

16

Javascripts

60

Images

4

CSS

18

AJAX

98

All

Possible request optimization

1

Javascripts

24

Images

1

CSS

18

AJAX

54

Optimized

44

All

Normal result

IP address

Aforz.biz uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

aforz.biz

rukinohakoniwa.sakura.ne.jp

gyokusai.tank.jp

uonuma-kome.com

tomcat.nyanta.jp

59.106.19.47

DNS records

Type Host Target/ip TTL Other
A

aforz.biz

59.106.19.47 300
NS

aforz.biz

ns1.dns.ne.jp 300
NS

aforz.biz

ns2.dns.ne.jp 300
SOA

aforz.biz

300 Mname: master.dns.ne.jp
Rname: tech.sakura.ad.jp
Serial: 2005112625
Refresh: 3600
Retry: 900
Expire: 3600000
Minimum-ttl: 3600
MX

aforz.biz

aforz.biz 300 Pri: 10

Language and encoding

Normal result

Language

JA ja language flag

Detected

JA ja language flag

Claimed

Encoding

SHIFT_JIS

Claimed

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

HTTPS certificate

SSL Certificate

Aforz.biz has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 100% of all visits is Japan. It’s good for Aforz.biz that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Poor result

Social Sharing Optimization

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

aforz.biz

Share this report in social media

Analyze another website

Analyze