10.9 sec in total
1.9 sec
8.8 sec
252 ms
Click here to check amazing 1 POST content for Japan. Otherwise, check out these important facts you probably never knew about 1post.jp
POSTは理学療法士、作業療法士、言語聴覚士のためのリハビリ情報サイトです。求人・転職などの就職情報から、セミナー、勉強会、講習会などの学会情報、お役立ち情報などを発信しています。
Visit 1post.jpWe analyzed 1post.jp page load time and found that the first response time was 1.9 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
1post.jp performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value15.4 s
0/100
25%
Value8.2 s
20/100
10%
Value510 ms
57/100
30%
Value0.27
45/100
15%
Value18.8 s
3/100
10%
1872 ms
357 ms
1326 ms
955 ms
361 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 40% of them (63 requests) were addressed to the original 1post.jp, 18% (28 requests) were made to O.twimg.com and 13% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain 1post.jp.
Page size can be reduced by 1.6 MB (12%)
12.7 MB
11.1 MB
In fact, the total size of 1post.jp main page is 12.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 11.6 MB which makes up the majority of the site volume.
Potential reduce by 45.6 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 45.6 kB or 77% of the original size.
Potential reduce by 730.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. 1 POST images are well optimized though.
Potential reduce by 346.1 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 346.1 kB or 73% of the original size.
Potential reduce by 458.0 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. 1post.jp needs all CSS files to be minified and compressed as it can save up to 458.0 kB or 85% of the original size.
Number of requests can be reduced by 72 (47%)
154
82
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1 POST. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
1post.jp
1872 ms
style.css
357 ms
bootstrap.css
1326 ms
app.css
955 ms
advanced-responsive-video-embedder-public.css
361 ms
ajax-load-more.css
548 ms
bbpress.css
785 ms
styles.css
507 ms
font-awesome.min.css
933 ms
bootstrap.css
1204 ms
front.css
1076 ms
swpm.common.css
982 ms
validationEngine.jquery.css
984 ms
screen.min.css
1113 ms
frontend.css
1203 ms
polls-css.css
1202 ms
jquery-ui-1.10.3.min.css
1254 ms
wpp.css
1292 ms
amazonjs.css
1354 ms
default.min.css
1367 ms
jquery.js
1768 ms
jquery-migrate.min.js
1323 ms
bootstrap.min.js
1579 ms
front.js
1444 ms
chosen.jquery.min.js
1490 ms
jquery.validationEngine-en.js
1515 ms
jquery.validationEngine.js
1720 ms
loader.js
127 ms
vertical-m.css
1489 ms
jquery-1.10.1.min.js
6 ms
main.js
1356 ms
customize.js
1401 ms
script.js
1543 ms
masonry.pkgd.min.js
1542 ms
imagesloaded.pkgd.min.js
1543 ms
jquery.validate.min.js
1610 ms
swpm-validation.js
1612 ms
jquery.metadata.js
1636 ms
messages-en_US.js
1637 ms
ajax-load-more.min.js
1680 ms
editor.js
1676 ms
jquery.form.min.js
1613 ms
scripts.js
1593 ms
front.min.js
1366 ms
polls-js.js
1370 ms
wp-embed.min.js
1268 ms
analytics.js
33 ms
wp-emoji-release.min.js
1047 ms
css
61 ms
collect
12 ms
post_logo.jpg
543 ms
8089e50294910c6cb163e5cb54ad137b4.png
736 ms
42afebe9b01aa3260c88e4399c55f7fd.png
1079 ms
q.jpg
561 ms
ooo-1.jpg
767 ms
w.jpg
566 ms
c7e2420f35196f4dcc211ade9af64c59.png
2407 ms
iii.jpg
766 ms
oo.jpg
758 ms
dk.png
1063 ms
book-mockup-free.png
5442 ms
ae46b1f460ee46f789c27b264a6cb421.png
2404 ms
e8a8246e347a77caccafc279bed7b55a.png
2595 ms
7b9f41895883397591044a0722eb8efa.png
1969 ms
20b2683d2b736f90b4497db3a5df68fc.jpg
2398 ms
bnr_melgaku.jpg
2157 ms
eb4e3872800dfa05148b29f4a3762496-e1458378078504.png
3053 ms
widgets.js
94 ms
mrk-footer-link.gif
3602 ms
all.js
23 ms
154 ms
xd_arbiter.php
25 ms
xd_arbiter.php
67 ms
ping
128 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
146 ms
page.php
325 ms
like_box.php
197 ms
syndication
88 ms
414259125090934784
335 ms
hQThvcX2PmE.css
50 ms
t3u7Vo4PVNb.css
51 ms
q68gy-v_YMF.js
58 ms
ehA1CqzHyzE.js
83 ms
0wM5s1Khldu.js
79 ms
1bNoFZUdlYZ.js
79 ms
10653415_1729773640602193_5510208881334725981_n.png
95 ms
10489904_1467453213500905_7281720272618842155_n.jpg
32 ms
1900014_422552541209615_838933368_n.jpg
68 ms
1383165_312931468858816_2466072216713523919_n.jpg
66 ms
1098283_211618778997859_454616773_n.jpg
67 ms
11796310_616584225150259_5572478925163751811_n.jpg
66 ms
12809752_1770242076520579_2989164686460927188_n.jpg
180 ms
11127554_792359297506549_3500570515106437952_n.jpg
182 ms
12249738_543461989146250_6238847262456186818_n.jpg
181 ms
wL6VQj7Ab77.png
43 ms
s7jcwEQH7Sx.png
13 ms
m83iJTM8ZQF.css
9 ms
vjfv3j-EdeX.css
26 ms
k19Xse48j5I.js
40 ms
ihptErjAmMX.js
25 ms
3So47A9WcrL.js
55 ms
cUsKAwzqrQw.js
62 ms
10653415_1729773640602193_5510208881334725981_n.png
30 ms
12814313_485438498315557_6788498361145768313_n.jpg
26 ms
10264909_404403869702554_1307785517846960806_n.jpg
26 ms
1934260_1762031084043115_943709397315765900_n.png
38 ms
10365937_1761868400726050_6978804067610498437_n.jpg
926 ms
1391510_1761697784076445_9084237355441301342_n.jpg
72 ms
1934144_1761470370765853_2967812275457949366_n.jpg
144 ms
1915832_1761418587437698_170083021609300022_n.jpg
36 ms
GtIpNnEyqq_.png
26 ms
I6-MnjEovm5.js
22 ms
pQrUxxo5oQp.js
24 ms
proxy.jpg
922 ms
proxy.jpg
74 ms
proxy.jpg
118 ms
proxy.jpg
180 ms
proxy.jpg
916 ms
proxy.jpg
76 ms
proxy.jpg
762 ms
proxy.jpg
339 ms
proxy.jpg
762 ms
proxy.jpg
761 ms
proxy.jpg
910 ms
proxy.jpg
916 ms
proxy.jpg
915 ms
proxy.jpg
916 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
35 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
63 ms
yLk6PqI5_normal.jpeg
862 ms
CdvuMUlUIAADqr3.jpg
870 ms
Cdqi5BJUUAApfFd.jpg
872 ms
CdqW-DMUEAA_QfJ.jpg
869 ms
CdlPacQVAAA8Lq8.jpg:large
868 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
62 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
66 ms
proxy.jpg
696 ms
proxy.jpg
411 ms
proxy.jpg
412 ms
proxy.jpg
162 ms
R9a_DtVRZgv.js
189 ms
cUDgRFxaoIk.js
189 ms
0JBr1QHp8Gi.js
190 ms
kDOzhTr2W91.js
189 ms
proxy.jpg
435 ms
proxy.jpg
244 ms
proxy.jpg
198 ms
proxy.jpg
139 ms
proxy.jpg
172 ms
proxy.jpg
145 ms
proxy.jpg
154 ms
proxy.jpg
189 ms
proxy.jpg
277 ms
proxy.jpg
234 ms
jot
29 ms
jot.html
28 ms
1post.jp 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
1post.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
1post.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1post.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 1post.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.
1post.jp
Open Graph description is not detected on the main page of 1 POST. 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: