Tools & Wizards About Us
junyx.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

junyx.net

JUNYX – Freelance IT Engineer – フリーランスITエンジニア

Page Load Speed

8 sec in total

First Response

2.1 sec

Resources Loaded

5 sec

Page Rendered

891 ms

junyx.net screenshot

About Website

Visit junyx.net now to see the best up-to-date JUNYX content and also check out these interesting facts you probably never knew about junyx.net

WordPress、Ruby on Rails、PHP、Linux、インターネット技術の解説などを書いています

Visit junyx.net

Key Findings

We analyzed Junyx.net page load time and found that the first response time was 2.1 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

junyx.net performance score

0

Network Requests Diagram

www.junyx.net

2107 ms

style.css

928 ms

jetpack.css

949 ms

prototype.js

28 ms

scriptaculous.js

29 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 56% of them (19 requests) were addressed to the original Junyx.net, 26% (9 requests) were made to Ajax.googleapis.com and 9% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Junyx.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 289.3 kB (43%)

Content Size

668.7 kB

After Optimization

379.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Junyx.net main page is 668.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. 30% of websites need less resources to load. Images take 281.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 53.6 kB

  • Original 68.7 kB
  • After minification 65.4 kB
  • After compression 15.1 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 53.6 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 7.0 kB

  • Original 281.9 kB
  • After minification 274.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. JUNYX images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 122.0 kB

  • Original 190.0 kB
  • After minification 182.3 kB
  • After compression 68.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 122.0 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 106.6 kB

  • Original 128.1 kB
  • After minification 111.0 kB
  • After compression 21.5 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. Junyx.net needs all CSS files to be minified and compressed as it can save up to 106.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (70%)

Requests Now

33

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.junyx.net

www.junyx.net

2107 ms

style.css

style.css

928 ms

jetpack.css

jetpack.css

949 ms

prototype.js

prototype.js

28 ms

scriptaculous.js

scriptaculous.js

29 ms

effects.js

effects.js

30 ms

lightbox.js

lightbox.js

827 ms

jquery.js

jquery.js

1334 ms

jquery-migrate.min.js

jquery-migrate.min.js

545 ms

wp-code-highlight.css

wp-code-highlight.css

585 ms

wp-code-highlight.js

wp-code-highlight.js

516 ms

devicepx-jetpack.js

devicepx-jetpack.js

4 ms

gprofiles.js

gprofiles.js

59 ms

wpgroho.js

wpgroho.js

442 ms

wp-embed.min.js

wp-embed.min.js

469 ms

e-201611.js

e-201611.js

3 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

206 ms

builder.js

builder.js

6 ms

effects.js

effects.js

8 ms

dragdrop.js

dragdrop.js

12 ms

controls.js

controls.js

18 ms

slider.js

slider.js

23 ms

sound.js

sound.js

22 ms

lightbox.css

lightbox.css

188 ms

cropped-2013-05-05-071.jpg

cropped-2013-05-05-071.jpg

386 ms

portable-hd-440x328.jpg

portable-hd-440x328.jpg

385 ms

Screenshot1s-440x247.png

Screenshot1s-440x247.png

589 ms

s-scr01-440x211.jpg

s-scr01-440x211.jpg

382 ms

s-2010-03-27-002.jpg

s-2010-03-27-002.jpg

400 ms

search.png

search.png

196 ms

comment-bubble.png

comment-bubble.png

197 ms

hovercard.css

hovercard.css

30 ms

services.css

services.css

58 ms

g.gif

g.gif

3 ms

SEO Factors

junyx.net SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

junyx.net

Open Graph data is detected on the main page of JUNYX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: