Analyze

nextframe.jp: フラッシュゲームサイト ネクストフレーム / FLASH GAME SITE NEXTFRAME(!)

ブラウザで手軽に遊べる無料のオリジナルゲームを配信。

Page load speed analysis

  • 54/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    987 ms

  • Resources loaded

    2.6 sec

  • Page rendered

    201 ms

  • Total page load time

    3.7 sec

Welcome to nextframe.jp homepage info - get ready to check NEXTFRAME best content for Japan right away, or after learning these important things about nextframe.jp

We analyzed Nextframe.jp page load time and found that the first response time was 987 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Page optimization

  • HTML 38.4 kB
    Images 399.1 kB
    Javascripts 142.2 kB
    CSS 0 B

    In fact, the total size of Nextframe.jp main page is 579.7 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 399.1 kB which makes up the majority of the site volume.

    • Original 38.4 kB
    • After minification 31.8 kB
    • After compression 5.2 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. This page needs HTML code to be minified as it can gain 6.6 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 33.2 kB or 86% of the original size.

    • Original 399.1 kB
    • After optimization 373.4 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. NEXTFRAME images are well optimized though.

    • Original 142.2 kB
    • After minification 142.1 kB
    • After compression 53.9 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 88.3 kB or 62% of the original size.

Network requests diagram

  • nextframe.jp
  • ga.js
  • __utm.gif
  • bg_sp_b_gry02.jpg
  • topHeaderGrf.jpg
  • top_NO1ICON.jpg
  • get_flash_player.gif
  • btn_top.jpg
  • btn_game.jpg
  • btn_trial.jpg
  • btn_blog.jpg
  • btn_about.jpg
  • btn_link.jpg
  • boxBig_ue.gif
  • 240x80_bs.jpg
  • 240x80_the2chBattle.jpg
  • boxBig_sita.gif
  • icon_star.jpg
  • top_index_01.jpg
  • tip_hori_01.gif
  • box_ue.gif
  • top_gunReport.jpg
  • box_sita.gif
  • top_rf.jpg
  • top_danmaku.jpg
  • top_mazuru.jpg
  • top_index_02.jpg
  • tip_hori_02.gif
  • top_meiro.gif
  • top_sokoabu.gif
  • top_pazuru.jpg
  • top_index_03.jpg
  • tip_hori_03.gif
  • top_seventhskyPlusTest.jpg
  • ssOld_top.jpg
  • picoPokky_top.gif
  • top_shooting.jpg
  • top_kadanmaku2.gif
  • top_index_04.jpg
  • tip_hori_04.gif
  • top_hosioi.gif
  • top_boon.jpg
  • top_easyBattle.jpg
  • top_allList.jpg
  • top_index_05.jpg
  • tip_hori_05.gif
  • howTo_top.gif
  • howto2_2_top.gif
  • index_books.gif
  • index_download.jpg
  • show_ads.js
  • ca-pub-6867115287170114.js
  • zrt_lookup.html
  • show_ads_impl.js
  • ads
  • osd.js
  • ads
  • null_image.gif
  • bunner_200x120_sspv_sdw.jpg
  • bunner_200x120_bsffpv_sdw.jpg
  • 13633876873245234745
  • abg.js
  • m_js_controller.js
  • googlelogo_color_112x36dp.png
  • G044a_120_120.jpg
  • G044a_124_240.jpg
  • null_image.gif
  • G051b_336_280.jpg
  • s
  • x_button_blue2.png
  • MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
  • btn_top_r.jpg
  • btn_game_r.jpg
  • btn_blog_r.jpg
  • btn_about_r.jpg
  • btn_link_r.jpg
  • btn_trial_r.jpg
  • ui
  • activeview

Our browser made a total of 79 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Nextframe.jp, 48% (38 requests) were made to Resource2.nextframe.jp and 18% (14 requests) were made to Resource.nextframe.jp. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Resource2.nextframe.jp.

Additional info on nextframe.jp

Requests

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

8

Javascripts

65

Images

4

AJAX

77

All

Possible request optimization

1

Javascripts

52

Images

4

AJAX

20

Optimized

57

All

Normal result

IP address

Nextframe.jp 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

nextframe.jp

digitaldj.jp

japan.digitaldj-network.com

longcompany.jp

digitaldj-network.com

59.106.13.190

DNS records

Type Host Target/ip TTL Other
A

nextframe.jp

59.106.13.190 3600
NS

nextframe.jp

ns2.dns.ne.jp 3600
NS

nextframe.jp

ns1.dns.ne.jp 3600
SOA

nextframe.jp

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

nextframe.jp

nextframe.jp 3600 Pri: 10

Language and encoding

Good result

Language

JA ja language flag

Detected

JA ja language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextframe.jp 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 Nextframe.jp 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.

HTTPS certificate

SSL Certificate

Nextframe.jp 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 87% of all visits is Japan. It’s good for Nextframe.jp 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 NEXTFRAME. 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:

nextframe.jp

Share this report in social media

Analyze another website

Analyze