Tools & Wizards About Us
next-21.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

next-21.co.jp

有限会社ネクスト-デザイン、広告、ホームページ、展示会ブース等の制作-

Page Load Speed

18.4 sec in total

First Response

770 ms

Resources Loaded

16.9 sec

Page Rendered

712 ms

next-21.co.jp screenshot

About Website

Welcome to next-21.co.jp homepage info - get ready to check Next 21 best content right away, or after learning these important things about next-21.co.jp

デザイン、広告、ホームページ制作、展示会、ステーショナリーなど制作を行っている有限会社ネクストです。防災商品等を扱うネットショップもあります。

Visit next-21.co.jp

Key Findings

We analyzed Next-21.co.jp page load time and found that the first response time was 770 ms and then it took 17.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

next-21.co.jp performance score

0

Network Requests Diagram

next-21.co.jp

770 ms

common.css

863 ms

jquery.min.js

75 ms

jquery.bxslider.min.js

898 ms

jquery.bxslider.css

416 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 87% of them (20 requests) were addressed to the original Next-21.co.jp, 9% (2 requests) were made to Ajax.googleapis.com and 4% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (15.4 sec) belongs to the original domain Next-21.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 321.2 kB (4%)

Content Size

9.0 MB

After Optimization

8.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Next-21.co.jp main page is 9.0 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. 15% of websites need less resources to load. Images take 9.0 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 5.4 kB

  • Original 7.9 kB
  • After minification 6.9 kB
  • After compression 2.5 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. This page needs HTML code to be minified as it can gain 1.0 kB, which is 13% 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 5.4 kB or 68% of the original size.

Image Optimization

-3%

Potential reduce by 279.6 kB

  • Original 9.0 MB
  • After minification 8.7 MB

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

JavaScript Optimization

-74%

Potential reduce by 14.4 kB

  • Original 19.4 kB
  • After minification 19.2 kB
  • After compression 5.0 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 14.4 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 21.8 kB

  • Original 25.6 kB
  • After minification 18.2 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. Next-21.co.jp needs all CSS files to be minified and compressed as it can save up to 21.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (14%)

Requests Now

22

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

next-21.co.jp

next-21.co.jp

770 ms

common.css

common.css

863 ms

jquery.min.js

jquery.min.js

75 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

898 ms

jquery.bxslider.css

jquery.bxslider.css

416 ms

jquery.min.js

jquery.min.js

61 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

73 ms

bg.jpg

bg.jpg

13878 ms

logo.png

logo.png

556 ms

tel.png

tel.png

564 ms

navi_bg.jpg

navi_bg.jpg

836 ms

main_bg.jpg

main_bg.jpg

15412 ms

main_image_1.png

main_image_1.png

3086 ms

main_image_2.png

main_image_2.png

5299 ms

main_image_3.png

main_image_3.png

5499 ms

copytxt.png

copytxt.png

2403 ms

design.jpg

design.jpg

3707 ms

digital.jpg

digital.jpg

4151 ms

exhibition.jpg

exhibition.jpg

5040 ms

title_bg_top.jpg

title_bg_top.jpg

4895 ms

banner_1.jpg

banner_1.jpg

5959 ms

banner_2.jpg

banner_2.jpg

6083 ms

totop.png

totop.png

5745 ms

SEO Factors

next-21.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

Social Sharing Optimization

next-21.co.jp

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