9.1 sec in total
585 ms
8.2 sec
357 ms
Visit president-navi.com now to see the best up-to-date President Navi content for Japan and also check out these interesting facts you probably never knew about president-navi.com
プレジデントナビでは正社員・契約社員・アルバイト・派遣のおしごとをまとめて検索できます。また、専任の弊社のおしごとコンサルタントがあなたをサポートします。
Visit president-navi.comWe analyzed President-navi.com page load time and found that the first response time was 585 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
president-navi.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value6.5 s
9/100
25%
Value5.2 s
60/100
10%
Value20 ms
100/100
30%
Value0.965
2/100
15%
Value7.3 s
50/100
10%
585 ms
1451 ms
851 ms
342 ms
361 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 94% of them (116 requests) were addressed to the original President-navi.com, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain President-navi.com.
Page size can be reduced by 217.5 kB (9%)
2.4 MB
2.2 MB
In fact, the total size of President-navi.com main page is 2.4 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. 45% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 41.4 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 6.6 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 41.4 kB or 79% of the original size.
Potential reduce by 115.8 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. President Navi images are well optimized though.
Potential reduce by 29.6 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 29.6 kB or 52% of the original size.
Potential reduce by 30.7 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. President-navi.com needs all CSS files to be minified and compressed as it can save up to 30.7 kB or 86% of the original size.
Number of requests can be reduced by 28 (23%)
121
93
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of President Navi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
president-navi.com
585 ms
www.president-navi.com
1451 ms
style.css
851 ms
li-scroller.css
342 ms
feature-carousel.css
361 ms
jquery-latest.js
46 ms
swfobject.js
535 ms
jquery.cookie.js
384 ms
actions.js
865 ms
slide_cont.js
538 ms
heightLine.js
575 ms
secom.js
170 ms
body_bg.jpg
184 ms
head_bg.jpg
187 ms
head_navi1.jpg
194 ms
head_navi2.jpg
185 ms
head_navi3.jpg
190 ms
head_navi4.jpg
192 ms
logo.jpg
350 ms
name2.jpg
519 ms
facebook.jpg
351 ms
navi_bg.jpg
361 ms
navi1.jpg
539 ms
navi8.jpg
577 ms
navi3.jpg
516 ms
navi7.jpg
522 ms
search.png
540 ms
search_btn.jpg
684 ms
main_bg2.jpg
3142 ms
main_content_bg2.png
1031 ms
scroller_bg2.gif
717 ms
all_bg.jpg
719 ms
title3.jpg
959 ms
job_search_bg2.jpg
851 ms
job_search_t2.jpg
1073 ms
job_search_t2.gif
898 ms
search3.jpg
1019 ms
job_search_t1.gif
1078 ms
open_arrow.png
1152 ms
title2.jpg
1186 ms
chara1_bg.jpg
1201 ms
chara1.jpg
1429 ms
chara1_btn.jpg
1256 ms
chara1_b.jpg
1342 ms
chara2_bg.jpg
1354 ms
chara2.jpg
1372 ms
chara2_btn.jpg
1436 ms
chara2_b.jpg
1504 ms
ga.js
17 ms
sdk.js
77 ms
__utm.gif
12 ms
collect
74 ms
128 ms
xd_arbiter.php
67 ms
xd_arbiter.php
128 ms
chara3_bg.jpg
1343 ms
chara3.jpg
1364 ms
chara3_btn.jpg
1424 ms
chara3_b.jpg
1430 ms
closeup_t.jpg
1668 ms
closeup_bg.jpg
1537 ms
1347236698-0.jpg
1542 ms
closeup_detail.jpg
1441 ms
1352178348-0.jpg
2012 ms
sp.png
1407 ms
login_bg.jpg
1452 ms
login_t.jpg
1506 ms
login_button.jpg
1524 ms
entry_button2.jpg
1576 ms
blog_bnr.jpg
1929 ms
new_job_bg.jpg
1512 ms
new_job_t.jpg
1514 ms
1437965300-0.jpg
2161 ms
-0.jpg
2011 ms
1437965239-0.jpg
3541 ms
1438155699-0.jpg
2127 ms
1437965335-0.jpg
2199 ms
1438058324-0.jpg
4003 ms
1438057915-0.jpg
4300 ms
1438327409-0.jpg
3255 ms
gs_bnr.jpg
2331 ms
tsushinkyujin-navi.jpg
2211 ms
kinyukyujin-navi.jpg
2375 ms
iwaikin_banner.jpg
2396 ms
20002065_01_75_JP.gif
2413 ms
to_top.jpg
2471 ms
foot_navi1.gif
2564 ms
foot_navi2.gif
2569 ms
foot_navi3.gif
2679 ms
foot_navi4.gif
2646 ms
foot_navi5.gif
2760 ms
foot_navi6.gif
2797 ms
foot_logo2.gif
2866 ms
copy.gif
2896 ms
secom.gif
2786 ms
foot_bg.jpg
2822 ms
head_navi1_over.jpg
2799 ms
head_navi2_over.jpg
2805 ms
head_navi3_over.jpg
2765 ms
head_navi4_over.jpg
2814 ms
facebook_over.jpg
2810 ms
navi1_over.jpg
2797 ms
navi8_over.jpg
2759 ms
navi3_over.jpg
2760 ms
navi7_over.jpg
2785 ms
search_btn_over.jpg
2659 ms
chara1_btn_over.jpg
2551 ms
chara2_btn_over.jpg
2264 ms
chara3_btn_over.jpg
2316 ms
closeup_detail_over.jpg
2115 ms
login_button_over.jpg
2062 ms
entry_button2_over.jpg
2015 ms
blog_bnr_over.jpg
1901 ms
gs_bnr_over.jpg
2070 ms
tsushinkyujin-navi_over.jpg
1796 ms
kinyukyujin-navi_over.jpg
1717 ms
iwaikin_banner_over.jpg
1655 ms
to_top_over.jpg
1645 ms
foot_navi1_over.gif
1607 ms
foot_navi2_over.gif
1569 ms
foot_navi3_over.gif
1429 ms
foot_navi4_over.gif
1423 ms
foot_navi5_over.gif
1347 ms
foot_navi6_over.gif
1378 ms
president-navi.com 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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
president-navi.com 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
Browser errors were logged to the console
president-navi.com 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise President-navi.com 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 President-navi.com 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.
president-navi.com
Open Graph description is not detected on the main page of President Navi. 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: