10.4 sec in total
999 ms
9 sec
321 ms
Visit modelcase.info now to see the best up-to-date Modelcase content and also check out these interesting facts you probably never knew about modelcase.info
株式会社モデルケースのブログです。日々進化を続けるソーシャル・スマートフォンなどITサービスに付いて雑感を書き連ねていきます。
Visit modelcase.infoWe analyzed Modelcase.info page load time and found that the first response time was 999 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
modelcase.info performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value2.9 s
80/100
25%
Value2.5 s
98/100
10%
Value100 ms
98/100
30%
Value0.029
100/100
15%
Value3.0 s
96/100
10%
999 ms
680 ms
717 ms
367 ms
386 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 25% of them (38 requests) were addressed to the original Modelcase.info, 25% (38 requests) were made to O.twimg.com and 10% (15 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (4.9 sec) relates to the external source I0.wp.com.
Page size can be reduced by 479.5 kB (26%)
1.8 MB
1.3 MB
In fact, the total size of Modelcase.info main page is 1.8 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. 75% 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 46.5 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 46.5 kB or 76% of the original size.
Potential reduce by 72.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. Modelcase images are well optimized though.
Potential reduce by 173.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 173.6 kB or 60% of the original size.
Potential reduce by 186.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. Modelcase.info needs all CSS files to be minified and compressed as it can save up to 186.6 kB or 75% of the original size.
Number of requests can be reduced by 79 (53%)
148
69
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Modelcase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.modelcase.info
999 ms
style.css
680 ms
dashicons.min.css
717 ms
thickbox.css
367 ms
styles-pre39.css
386 ms
shortcodes.css
392 ms
jetpack.css
572 ms
jquery.js
928 ms
jquery-migrate.min.js
570 ms
jquery.tipsy.js
583 ms
tie-scripts.js
756 ms
innerfade.js
757 ms
external-tracking.min.js
774 ms
style-green.css
845 ms
css
25 ms
jquery.min.js
10 ms
noteit.js
35 ms
platform.js
59 ms
photon.js
715 ms
auto-thickbox.min.js
792 ms
devicepx-jetpack.js
25 ms
gprofiles.js
71 ms
wpgroho.js
791 ms
wp-embed.min.js
791 ms
google-analytics.min.js
869 ms
e-201611.js
25 ms
conversion.js
43 ms
common.js
914 ms
wp-emoji-release.min.js
449 ms
sdk.js
375 ms
dc.js
50 ms
fbds.js
417 ms
bnr_lineStamp.png
4879 ms
body-bg1.png
405 ms
btn_mail01.png
405 ms
rss_16.png
222 ms
google_plus_16.png
249 ms
facebook_16.png
403 ms
twitter_16.png
403 ms
linkedin_16.png
446 ms
MC_blog03_281.png
445 ms
btn_mail02.png
605 ms
img_blogBanner01_off.png
605 ms
img_blogBanner03_off.png
604 ms
widgets.js
83 ms
main-menu-bg.png
598 ms
s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff
26 ms
EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff
25 ms
stripe.png
595 ms
sidebar-bullet.png
603 ms
BebasNeue-webfont.woff
756 ms
plusone.js
49 ms
quote.png
703 ms
__utm.gif
23 ms
cb=gapi.loaded_0
25 ms
cb=gapi.loaded_1
60 ms
fastbutton
195 ms
badge
237 ms
63 ms
g.gif
35 ms
like.php
479 ms
385 ms
postmessageRelay
175 ms
352 ms
hovercard.css
113 ms
services.css
241 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
358 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
380 ms
cb=gapi.loaded_0
53 ms
cb=gapi.loaded_1
51 ms
loadingAnimation.gif
429 ms
rs=AGLTcCObu_AspndiuVgsAof6R5t3WzcDSA
60 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
69 ms
rs=AGLTcCON5xo3PJKQK4uCrXLJLysK2Nj1Xw
110 ms
3193398744-postmessagerelay.js
215 ms
rpc:shindig_random.js
198 ms
565 ms
202 ms
xd_arbiter.php
328 ms
xd_arbiter.php
533 ms
rs=AGLTcCON5xo3PJKQK4uCrXLJLysK2Nj1Xw
42 ms
grlryt2bdKIyfMSOhzd1eA.woff
98 ms
d-QWLnp4didxos_6urzFtg.woff
102 ms
vxNK-E6B13CyehuDCmvQvw.woff
118 ms
rs=AGLTcCON5xo3PJKQK4uCrXLJLysK2Nj1Xw
17 ms
cb=gapi.loaded_0
9 ms
qeKvIRsJabD.js
493 ms
LVx-xkvaJ0b.png
553 ms
syndication
133 ms
316887403270914048
493 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
54 ms
proxy.jpg
106 ms
proxy.jpg
96 ms
proxy.jpg
68 ms
proxy.jpg
61 ms
proxy.jpg
90 ms
proxy.jpg
90 ms
proxy.jpg
177 ms
proxy.jpg
177 ms
proxy.jpg
182 ms
proxy.jpg
176 ms
proxy.jpg
176 ms
proxy.jpg
180 ms
proxy.jpg
180 ms
proxy.jpg
180 ms
proxy.jpg
195 ms
proxy.jpg
180 ms
proxy.jpg
234 ms
proxy.jpg
220 ms
proxy.jpg
234 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
30 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
60 ms
logo_modelcase_face_normal.jpg
215 ms
BxTuq1hCEAAEQa8.png:small
772 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
45 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
115 ms
proxy.jpg
60 ms
proxy.jpg
62 ms
proxy.jpg
45 ms
proxy.jpg
26 ms
proxy.jpg
80 ms
proxy.jpg
27 ms
proxy.jpg
47 ms
proxy.jpg
54 ms
proxy.jpg
38 ms
proxy.jpg
26 ms
proxy.jpg
65 ms
proxy.jpg
30 ms
proxy.jpg
45 ms
proxy.jpg
40 ms
proxy.jpg
26 ms
proxy.jpg
28 ms
proxy.jpg
36 ms
proxy.jpg
27 ms
proxy.jpg
42 ms
jot.html
30 ms
21 ms
page.php
455 ms
m83iJTM8ZQF.css
74 ms
q68gy-v_YMF.js
143 ms
k19Xse48j5I.js
338 ms
ihptErjAmMX.js
274 ms
393827_270542653011749_1530048547_n.jpg
357 ms
11921859_134301273580906_8807891108304725917_n.jpg
424 ms
430085_265646796888679_1374143702_n.jpg
566 ms
12523859_242629899413918_1699176569700383791_n.jpg
622 ms
315642_119363828168459_789724661_n.jpg
557 ms
12115866_956051051140349_3843400371268171087_n.jpg
559 ms
10568799_1516953518517459_5191374053969511451_n.jpg
557 ms
wL6VQj7Ab77.png
75 ms
s7jcwEQH7Sx.png
75 ms
R9a_DtVRZgv.js
71 ms
cUDgRFxaoIk.js
69 ms
0JBr1QHp8Gi.js
73 ms
kDOzhTr2W91.js
71 ms
modelcase.info 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
<frame> or <iframe> elements do not have a title
modelcase.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
modelcase.info 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
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Modelcase.info can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Modelcase.info 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.
modelcase.info
Open Graph description is not detected on the main page of Modelcase. 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: