keisukekanda
by
MakotoHonda
from Japan
-
0Friendliness
-
0Performance
-
0Usability
-
0PWA
-
0Total
Find out more about the Evaluation
Performance 30/100
Speed Index
-
Speed Index15856target < 4000 ms
The Speed Index measures how quickly the page contents are visually populated / painted, and computes an overall score where lower numbers are better. It is expressed in milliseconds and dependent on size of the viewport (above-the-fold contents). Learn more
Document complete
-
Time15.9seconds
-
Resources126requests
-
Bytes in7.7MB
These metrics are collected from the initial request until the browser considers the page loaded (JavaScript onLoad event). This usually happens after all of the image content has loaded but may not include content that is triggered by javascript execution.
Fully load
-
Time15.9seconds
-
Resources128requests
-
Bytes in7.7MB
These metrics are collected from the initial request until 2 seconds of no network activity after Document Complete (JavaScript onLoad event). This will usually include any activity that is triggered by javascript after the main page loads.
Assets by Domain
Requests
- www.keisukekanda.com
- pbs.twimg.com
- calendar.google.com
- platform.twitter.com
- apis.google.com
- syndication.twitter.com
- clients6.google.com
- abs.twimg.com
- netdna.bootstrapcdn.com
- www.gstatic.com
- www.google.com
- cdn.syndication.twimg.com
- ton.twimg.com
Bytes downloaded
- www.keisukekanda.com
- pbs.twimg.com
- apis.google.com
- calendar.google.com
- netdna.bootstrapcdn.com
- platform.twitter.com
- cdn.syndication.twimg.com
- ton.twimg.com
- abs.twimg.com
- www.gstatic.com
- clients6.google.com
- syndication.twitter.com
Assets by Mime-Type
Requests
- html
- js
- css
- image
- font
- other
Bytes downloaded
- html
- js
- css
- image
- font
- other
Speed
Load time15888 ms
Also known as the document complete time, it’s the time from the initial request until the browser load event. It can vary based on server location, device, browser, and third-party apps. Learn more
Page load is fast enough on 3G
A fast page load over a 3G network ensures a good mobile user experience. Learn more
First byte2699 ms
The time from the initial request to the first byte of the response. Learn more
First meaningful paint14001 ms
First meaningful paint measures when the primary content of a page is visible. It's essentially the paint after which the biggest above-the-fold layout change has happened, and web fonts have loaded. Learn more
Estimated Input Latency16 ms (target < 50 ms)
The score above is an estimate of how long your app takes to respond to user input, in milliseconds. There is a 90% probability that a user encounters this amount of latency, or less. 10% of the time a user can expect additional latency. If your score is higher than Lighthouse's target score (< 50 ms), users may perceive your app as laggy. Learn more
Uses persistent connections (keep alive)Score: 100%
Closing connections are a missed opportunity for performance enhancement: additional round-trips between the user and the server to initiate a connection is redundant and time-consuming. Keep-Alive measures the effectiveness of connection reuse. The purpose of this grade is to evaluate the extent to which requests are inefficiently reopening connections. Learn more
First interactive (beta - experimental)15719.5 ms
The first point at which necessary scripts of the page have loaded and the CPU is idle enough to handle most user input (with the possibility of slow responses as more content loads). Learn more
Consistently Interactive (beta - experimental)Not applicable
The point at which most network resources have finished loading and the CPU is idle for a prolonged period. Consistently Interactive requires a minimum of 5 seconds of both main thread idle and network idle. In other words, the point where the page is complete and will respond quickly to user input. Learn more
Page weight
Uses compression (gzip, zopfli, deflate, brotli)Score: 29%
This rule triggers when detecting that compressible resources were served without gzip compression. Learn more
Uses a CDN for all static assetsScore: 97%
Each request for a piece of content to the web server has to travel from the user's browser all the way to the server and back. A content delivery network (CDN) is a system for distributing resources to servers geographically closer to users. Main benefit of this is that the round-trip time is faster. The passing grade for using a CDN effectively is to have at least 80% of static resources served from a CDN. Learn more
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network. Learn more
Leverage browser caching for the following cacheable resources:
| URL |
|---|
| http://www.keisukekanda.com/commons/font/migu/migu-1m-regular.ttf (expiration not specified) |
| http://www.keisukekanda.com/commons/font/migu/migu-1m-regular.woff (expiration not specified) |
| https://cdn.syndication.twimg.com/timeline/profile?callback=__twttr.callbacks.tl_i0_profile_keisuke_kanda_old&dnt=false&domain=www.keisukekanda.com&lang=ja&screen_name=keisuke_kanda&suppress_response_codes=true&t=1709419&tz=GMT-0700&with_replies=false (5 minutes) |
| https://syndication.twitter.com/settings (10 minutes) |
| https://apis.google.com/js/client.js?onload=clientLibraryLoaded (30 minutes) |
| https://apis.google.com/js/googleapis.proxy.js?onload=startup (30 minutes) |
| https://platform.twitter.com/widgets.js (30 minutes) |
... |
Minify CSS
Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Learn more
Minify CSS for the following resources to reduce their size by 68KiB (21% reduction).
| URL |
|---|
| Minifying http://www.keisukekanda.com/commons/news/html/css/cms.css could save 22.9KiB (31% reduction). |
| Minifying http://www.keisukekanda.com/commons/css/animate.css could save 12.2KiB (18% reduction). |
| Minifying http://www.keisukekanda.com/commons/assets/buttons/css/buttons.css could save 11.8KiB (17% reduction). |
| Minifying http://www.keisukekanda.com/commons/css/helper.css could save 8.6KiB (14% reduction). |
| Minifying http://www.keisukekanda.com/commons/news/html/css/site.css could save 4.4KiB (36% reduction). |
| Minifying http://www.keisukekanda.com/commons/assets/flexboxgrid/css/flexboxgrid.css could save 3.1KiB (23% reduction). |
| Minifying http://www.keisukekanda.com/commons/assets/featherlight/src/featherlight.css could save 1.8KiB (51% reduction). |
| Minifying http://www.keisukekanda.com/commons/css/index.css could save 1.8KiB (12% reduction). |
| Minifying http://www.keisukekanda.com/commons/css/reboot.css could save 990B (21% reduction). |
| Minifying http://www.keisukekanda.com/commons/news/html/css/free.css could save 397B (43% reduction). |
... |
Minify HTML
Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Learn more
Minify HTML for the following resources to reduce their size by 280B (11% reduction).
| URL |
|---|
| Minifying http://www.keisukekanda.com/commons/news/event/news.html could save 143B (11% reduction). |
| Minifying http://www.keisukekanda.com/commons/news/event/ticker.html could save 137B (11% reduction). |
... |
Minify JavaScript
Minification refers to the process of removing unnecessary or redundant data in order to reduce file size without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. Learn more
Minify JavaScript for the following resources to reduce their size by 232.1KiB (53% reduction).
| URL |
|---|
| Minifying http://www.keisukekanda.com/commons/js/jquery-3.3.1.js could save 129.5KiB (49% reduction). |
| Minifying http://www.keisukekanda.com/commons/assets/scrollmagic/scrollmagic/uncompressed/ScrollMagic.js could save 66.7KiB (65% reduction). |
| Minifying http://www.keisukekanda.com/commons/assets/scrollmagic/scrollmagic/uncompressed/plugins/debug.addIndicators.js could save 11.6KiB (50% reduction). |
| Minifying http://www.keisukekanda.com/commons/assets/featherlight/src/featherlight.js could save 11.5KiB (50% reduction). |
| Minifying http://www.keisukekanda.com/commons/assets/scrollmagic/scrollmagic/uncompressed/plugins/animation.gsap.js could save 7.7KiB (66% reduction). |
| Minifying http://www.keisukekanda.com/commons/js/jquery.smooth-scroll.js could save 3.7KiB (48% reduction). |
| Minifying http://www.keisukekanda.com/commons/news/html/js/site.js could save 1KiB (57% reduction). |
| Minifying http://www.keisukekanda.com/commons/ajax-counter/counter.js could save 301B (38% reduction). |
... |
Avoids an excessive DOM size3592 nodes
Number of elements in the document. Browser engineers recommend pages contain fewer than ~1,500 DOM nodes. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more
-
Total DOM Nodes3,592target < 1,500 nodes
-
DOM Depth12target < 32
-
Maximum Children248target < 60 nodes
Compressed ImagesPotential savings of 1,113 KB (~6,020 ms)
The image compression check just looks at photo images and makes sure the quality isn't set too high. Images can usually be compressed pretty substantially without any noticeable reduction in visual quality. Learn more
| Thumbnails | URL | Original | Potential Savings |
|---|---|---|---|
 | http://www.keisukekanda.com/commons/img/index/logo-creephyp.jpg | 664 KB | 622 KB (94%) |
 | http://www.keisukekanda.com/commons/img/index/mainvisual.jpg | 364 KB | 216 KB (59%) |
 | http://www.keisukekanda.com/commons/news/images/134725561_th.jpg | 200 KB | 162 KB (81%) |
 | http://www.keisukekanda.com/commons/img/index/logo-asicsANREALAGE.jpg | 59 KB | 32 KB (53%) |
 | http://www.keisukekanda.com/commons/img/index/logo-dddd.jpg | 68 KB | 30 KB (44%) |
 | http://www.keisukekanda.com/commons/img/index/logo-beams.jpg | 37 KB | 19 KB (52%) |
 | http://www.keisukekanda.com/commons/img/index/logo-bunka.jpg | 38 KB | 14 KB (37%) |
 | http://www.keisukekanda.com/commons/img/index/logo-gingnang.jpg | 31 KB | 11 KB (35%) |
 | http://www.keisukekanda.com/commons/img/index/logo-misakitanaka.jpg | 20 KB | 7 KB (35%) |
... |
|||
Uses Progressive JPEGsScore: 59 %
A progressive JPEG is image created using the JPEG suite of compression algorithms that will 'fade in' in successive waves of lines until the entire image has completely arrived. They show the entire image right away, looking slightly pixelated until the image data is fully loaded. Learn more
Properly Sized ImagesPotential savings of 810 KB (~4,390 ms)
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more
Offscreen imagesPotential savings of 668 KB (~3,620 ms)
Consider lazy-loading offscreen images to improve page load speed and time to interactive. Learn more
First impression
Eliminates render-blocking JavaScript and CSS in above-the-fold content
This rule triggers when detecting that your HTML references a blocking external resource / file in the above-the-fold portion of your page. Learn more about JS - Learn more about CSS
Your page has 8 blocking script resources and 8 blocking CSS resources. This causes a delay in rendering your page.
| URL |
|---|
| http://www.keisukekanda.com/commons/js/jquery-3.3.1.js |
| http://www.keisukekanda.com/commons/assets/scrollmagic/js/lib/greensock/TweenMax.min.js |
| http://www.keisukekanda.com/commons/assets/scrollmagic/scrollmagic/uncompressed/ScrollMagic.js |
| http://www.keisukekanda.com/commons/assets/scrollmagic/scrollmagic/uncompressed/plugins/animation.gsap.js |
| http://www.keisukekanda.com/commons/assets/scrollmagic/scrollmagic/uncompressed/plugins/debug.addIndicators.js |
| http://www.keisukekanda.com/commons/ajax-counter/counter.js |
| http://www.keisukekanda.com/commons/assets/featherlight/src/featherlight.js |
| http://www.keisukekanda.com/commons/js/jquery.smooth-scroll.js |
| http://www.keisukekanda.com/commons/css/reboot.css |
| http://www.keisukekanda.com/commons/css/index.css |
| http://www.keisukekanda.com/commons/font/kk/style.css |
| http://www.keisukekanda.com/commons/css/helper.css |
| http://www.keisukekanda.com/commons/css/animate.css |
| http://www.keisukekanda.com/commons/assets/flexboxgrid/css/flexboxgrid.css |
| http://www.keisukekanda.com/commons/assets/buttons/css/buttons.css |
| http://www.keisukekanda.com/commons/assets/featherlight/src/featherlight.css |
... |
Prioritizes visible content
This rule triggers when detecting that additional network round trips are required to render the above-the-fold content of the page. Learn more
Improves server response time
This rule triggers when detecting that your server response time is above 200 ms. Server response time measures how long it takes to load the necessary HTML to begin rendering the page from your server, subtracting out the network latency between Google and your server. Learn more
Avoids landing page redirects
Redirects trigger an additional HTTP request-response cycle and delay page rendering. In the best case, each redirect will add a single round trip (HTTP request-response), and in the worst it may result in multiple additional roundtrips to perform the DNS lookup, TCP handshake, and TLS negotiation in addition to the additional HTTP request-response cycle. As a result, you should minimize use of redirects to improve site performance. Learn more
Report created in Oct 03, 2018, 13:55 PM GMT+0 min.
This report was built using several Google, 3rd-party and Awwwards audit tools and services for metrics, web performance optimization, and best practices for mobile design and development.
Loading time vary depending on network, device, server, site design, and implementation.
These are the environments used to create this report:
| Webpagetest | Test Location | Dulles VA USA |
| Browser | MotoG4 Chrome | |
| Connection | Mobile 3G (1.6 Mbps / 768 Kbps 300ms RTT) | |
| Number of Runs | 1 | |
| User Agent | Default | |
| Lighthouse | User agent | Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5 Build/MRA58N) AppleWebKit/537.36(KHTML, like Gecko) Chrome/61.0.3116.0 Mobile Safari/537.36 |
| Device Emulation | Nexus 5X o MotoG | |
| Network Throttling | 1.4Mbps down, 0.7Mbps up, 562.5ms RTT (PageSpeed uses Chrome on Moto G4 within a 3G network) | |
| CPU Throttling | 4x slowdown | |
| PageSpeed Insights Mobile | Environment | Default |
| TestMySite | Environment | Default |