7.9 sec in total
1.1 sec
6.5 sec
272 ms
Welcome to 10409.jp homepage info - get ready to check 10409 best content right away, or after learning these important things about 10409.jp
第二新卒と20代の転職ノウハウとは。転職のやり方や年収、キャリア、人生などについて発信します。
Visit 10409.jpWe analyzed 10409.jp page load time and found that the first response time was 1.1 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
10409.jp performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value5.0 s
27/100
25%
Value5.1 s
61/100
10%
Value120 ms
97/100
30%
Value0.002
100/100
15%
Value6.1 s
63/100
10%
1089 ms
354 ms
367 ms
497 ms
339 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 93% of them (77 requests) were addressed to the original 10409.jp, 1% (1 request) were made to Seal.websecurity.norton.com and 1% (1 request) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain 10409.jp.
Page size can be reduced by 151.8 kB (40%)
376.6 kB
224.8 kB
In fact, the total size of 10409.jp main page is 376.6 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. 15% of websites need less resources to load. Images take 181.2 kB which makes up the majority of the site volume.
Potential reduce by 27.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 27.1 kB or 77% of the original size.
Potential reduce by 4.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. 10409 images are well optimized though.
Potential reduce by 55.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 55.3 kB or 66% of the original size.
Potential reduce by 64.6 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. 10409.jp needs all CSS files to be minified and compressed as it can save up to 64.6 kB or 85% of the original size.
Number of requests can be reduced by 36 (44%)
81
45
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 10409. 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 from 11 to 1 for CSS and as a result speed up the page load time.
10409.jp
1089 ms
import.css
354 ms
common.js
367 ms
common.css
497 ms
subpage.css
339 ms
index.css
702 ms
regist.css
377 ms
mypage.css
760 ms
search.css
820 ms
beginner.css
738 ms
guide.css
748 ms
others.css
987 ms
popup.css
1048 ms
getseal
392 ms
urchin.js
26 ms
conversion.js
28 ms
main_bg.gif
684 ms
header.jpg
495 ms
header_menu_a.jpg
499 ms
arrow_1_green.gif
364 ms
index_news_bg_middle.jpg
354 ms
index_news_bg_top.jpg
365 ms
index_image.jpg
1277 ms
index_btregist_bt_a.jpg
736 ms
index_bg_middle.jpg
741 ms
index_bg_top.jpg
999 ms
index_bg_bottom.jpg
838 ms
index_pickup_bg_middle.gif
1008 ms
index_pickup_bg_bottom.gif
1079 ms
index_special.jpg
1101 ms
index_special_bg.gif
1178 ms
index_new.jpg
1331 ms
index_new_bg.gif
1349 ms
search_title-kai.gif
1583 ms
search_bg_middle-kai.gif
1428 ms
search_kantan-kai.gif
1533 ms
search_kantan_bg_bottom-kai.gif
1636 ms
search_bg_top-kai.gif
1688 ms
search_bg_bottom-kai.gif
1677 ms
search_kodawari.gif
1770 ms
search_occupational.gif
1884 ms
search_industrial.gif
1926 ms
search_district.gif
1998 ms
search_keyword.gif
2006 ms
search_bt_a.gif
2021 ms
search_bg_bottom2-kai.gif
2135 ms
index_oyakudachi_bg.gif
2255 ms
index_tool_title.gif
2306 ms
index_tool_bg_middle.gif
2350 ms
index_tool_bg_top.gif
2374 ms
index_tool_bg_bottom.gif
2375 ms
1.jpg
2623 ms
__utm.gif
7 ms
36 ms
31 ms
index_tool_bt_a.gif
2220 ms
2.jpg
2474 ms
3.jpg
2492 ms
column_bana.jpg
2781 ms
index_guide_title.gif
2242 ms
index_guide_1_new.jpg
2401 ms
index_guide_b.jpg
2263 ms
index_guide_2_new.jpg
2499 ms
index_guide_3_new.jpg
2513 ms
index_guide_4_new.jpg
2370 ms
index_guide_5_new.jpg
2517 ms
index_login_bg_middle.gif
2340 ms
index_login_bg_top.gif
2469 ms
index_login_white_bg_middle.gif
2435 ms
index_login_white_bg_top.gif
2423 ms
index_login_title_regist.gif
2423 ms
index_login_white_bg_bottom.gif
2410 ms
index_login_title_login.gif
2459 ms
index_login_bt_login_a.gif
2378 ms
index_login_title_mobile.gif
2401 ms
index_login_mobile_qr.gif
2414 ms
index_login_mobile_url.gif
2395 ms
index_login_mobile_bt_a.gif
2448 ms
index_login_bg_bottom.gif
2458 ms
bn170_70.png
2567 ms
banner_cv.gif
2542 ms
bn-blog_lahosuclub.gif
2539 ms
header_menu_bg.jpg
2469 ms
10409.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
10409.jp 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
10409.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 10409.jp 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 10409.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.
10409.jp
Open Graph description is not detected on the main page of 10409. 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: