4.7 sec in total
598 ms
3.9 sec
179 ms
Visit pocket9.net now to see the best up-to-date Pocket 9 content for Japan and also check out these interesting facts you probably never knew about pocket9.net
シンプルですぐに使える勤怠管理システム PocketTime、IT技術・一般業務者の業務経歴を一括管理 経歴管理システム PocketResume、問題配信管理機能でEラーニング ケータイナレッジ、Pocketシリーズの機能が集約されたグループウェア PocketBiz、を提供致します。
Visit pocket9.netWe analyzed Pocket9.net page load time and found that the first response time was 598 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pocket9.net performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value12.1 s
0/100
25%
Value9.4 s
12/100
10%
Value170 ms
93/100
30%
Value0.078
95/100
15%
Value9.4 s
31/100
10%
598 ms
861 ms
198 ms
395 ms
490 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 69% of them (25 requests) were addressed to the original Pocket9.net, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Pocket9.net.
Page size can be reduced by 81.3 kB (9%)
918.9 kB
837.6 kB
In fact, the total size of Pocket9.net main page is 918.9 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 642.0 kB which makes up the majority of the site volume.
Potential reduce by 34.0 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 34.0 kB or 84% of the original size.
Potential reduce by 10.7 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. Pocket 9 images are well optimized though.
Potential reduce by 33.3 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 33.3 kB or 24% of the original size.
Potential reduce by 3.3 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. Pocket9.net has all CSS files already compressed.
Number of requests can be reduced by 18 (55%)
33
15
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pocket 9. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
pocket9.net
598 ms
pocket9.net
861 ms
all.min.css
198 ms
style.min.css
395 ms
block-build.css
490 ms
front.css
658 ms
vkExUnit_style.css
496 ms
style.css
593 ms
style.css
680 ms
common.css
683 ms
jquery.min.js
819 ms
jquery-migrate.min.js
660 ms
front.js
787 ms
chosen.jquery.min.js
833 ms
css
55 ms
jquery.min.js
44 ms
bootstrap.min.js
54 ms
jquery.inview.min.js
60 ms
wqk3lhzygxy8lmzbtgiedt8filg1iqbq.js
175 ms
wp-embed.min.js
854 ms
render.ab0ffde36be6aa7a153d.js
47 ms
analytics.js
70 ms
vk-menu-btn-black.svg
264 ms
titlelogo.gif
263 ms
6c4fdac023ad0ad45d8a362104bf1c77-1.png
1631 ms
1a6ad80976a646f19ff23a360c8e593d.jpg
703 ms
7759bebead7f3290720a29f056378995.jpg
1183 ms
fa5938bc9e3ed0405e43e8928d16108f.jpg
373 ms
icon_115962_256-150x150.png
374 ms
icon_155402_256-150x150.png
437 ms
icon_153042_256-150x150.png
537 ms
icon_111222_256-150x150.png
537 ms
collect
12 ms
collect
33 ms
js
74 ms
ga-audiences
150 ms
pocket9.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
pocket9.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
pocket9.net SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pocket9.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 Pocket9.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.
pocket9.net
Open Graph description is not detected on the main page of Pocket 9. 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: