6.8 sec in total
577 ms
6 sec
201 ms
Click here to check amazing JILLE content. Otherwise, check out these important facts you probably never knew about jille.jp
雑誌ジル【JILLE】のオフィシャルサイト。モデル今宿麻美のブログやコミュニティ。誌面の立ち読みも出来ますよ♪
Visit jille.jpWe analyzed Jille.jp page load time and found that the first response time was 577 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
jille.jp performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value12.7 s
0/100
25%
Value9.2 s
13/100
10%
Value160 ms
93/100
30%
Value0.216
58/100
15%
Value6.8 s
55/100
10%
577 ms
345 ms
356 ms
899 ms
366 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 46% of them (50 requests) were addressed to the original Jille.jp, 19% (20 requests) were made to Scontent.cdninstagram.com and 13% (14 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Jille.jp.
Page size can be reduced by 189.0 kB (20%)
925.3 kB
736.3 kB
In fact, the total size of Jille.jp main page is 925.3 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. 40% of websites need less resources to load. Images take 652.3 kB which makes up the majority of the site volume.
Potential reduce by 33.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 33.0 kB or 73% of the original size.
Potential reduce by 2.4 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. JILLE images are well optimized though.
Potential reduce by 135.5 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 135.5 kB or 66% of the original size.
Potential reduce by 18.2 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. Jille.jp needs all CSS files to be minified and compressed as it can save up to 18.2 kB or 82% of the original size.
Number of requests can be reduced by 67 (68%)
99
32
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JILLE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
jille.jp
577 ms
base.css
345 ms
top.css
356 ms
jquery-1.8.3.min.js
899 ms
jquery.easing.1.3.js
366 ms
jquery.page-scroller-308.js
387 ms
jquery.clock.js
379 ms
jquery.cycle.all.min.js
845 ms
jsapi
20 ms
jsapi
42 ms
getFeed.js
696 ms
getFeed_buyer.js
721 ms
getFeed01.js
741 ms
getFeed02.js
744 ms
jquery.tinyscrollbar.min.js
1063 ms
instagram.js
1077 ms
top.js
1126 ms
13 ms
default+en.css
3 ms
default+en.I.js
4 ms
analytics.js
55 ms
logobg.jpg
199 ms
logo.gif
349 ms
gnv01_on.gif
358 ms
gnv02_new.gif
379 ms
snvbg.gif
374 ms
snv02.gif
383 ms
snv04.gif
529 ms
bn03.gif
1196 ms
bn01.jpg
1293 ms
bn02.gif
999 ms
menu01.gif
851 ms
menu02.gif
844 ms
menu03.gif
919 ms
slide_nav_bg.gif
1169 ms
slide_nav02.gif
1230 ms
slide_nav03.gif
1269 ms
slide_img02_0731.gif
1883 ms
slide_img03_new.jpg
3399 ms
editors_room_ttl.png
1541 ms
catch_up_news_ttl.png
1576 ms
r_section_bg.png
1655 ms
tw_ttl.png
1646 ms
tw_btn.png
1902 ms
insta_ttl.png
1905 ms
insta_l_btn.png
2001 ms
insta_r_btn.png
2010 ms
insta_btn.png
2252 ms
fb_ttl.png
2295 ms
fb_btn.png
2289 ms
pgup.gif
2352 ms
copy.gif
2354 ms
fnv01.gif
2596 ms
widgets.js
28 ms
2.gif
542 ms
recent
355 ms
r_section_bg_bottom.png
2605 ms
footbg.gif
2605 ms
0.gif
548 ms
mon3.gif
554 ms
1.gif
556 ms
6.gif
561 ms
am.gif
586 ms
colon.gif
900 ms
3.gif
889 ms
4.gif
924 ms
collect
12 ms
12298790_1638023689798274_789259061_n.jpg
232 ms
11820566_522308057926569_517364979_n.jpg
273 ms
11363639_1761603294066786_461015732_n.jpg
353 ms
11084655_368596239996952_42175911_n.jpg
324 ms
10948753_1429202284046099_992379670_n.jpg
321 ms
11101981_648315645301758_1346005373_n.jpg
330 ms
10747901_369525526559171_703713409_n.jpg
340 ms
10755801_1495011170760520_425507958_n.jpg
302 ms
10723819_522463461189305_1139990636_n.jpg
358 ms
10727527_1578640195697388_562637573_n.jpg
375 ms
925334_1496272477298966_1534968619_n.jpg
363 ms
10725036_1487821681482754_2091567598_n.jpg
400 ms
1390412_1478811492396247_1929049593_n.jpg
436 ms
10598660_593759017401412_63001652_n.jpg
433 ms
10413133_348405675308901_1654381968_n.jpg
385 ms
10547203_250482105151052_1316616322_n.jpg
443 ms
1516649_663966293639244_668155307_n.jpg
457 ms
927678_512329558872949_2131136975_n.jpg
412 ms
11417331_1630640590551491_498853225_n.jpg
479 ms
11357600_935481576474035_113691077_n.jpg
458 ms
5.gif
187 ms
print.css
181 ms
Gfeeds
209 ms
Gfeeds
198 ms
Gfeeds
289 ms
Gfeeds
476 ms
Gfeeds
466 ms
Gfeeds
171 ms
Gfeeds
364 ms
Gfeeds
466 ms
Gfeeds
375 ms
10009300_258211914360240_2119035935_n.jpg
217 ms
safe_image.php
298 ms
safe_image.php
270 ms
1896941_247450598769705_577383313_n.jpg
174 ms
1618694_246473618867403_1481434578_n.jpg
188 ms
1017635_238297916351640_1397288860_n.jpg
187 ms
1003916_233728970141868_616919280_n.jpg
183 ms
601204_222924411222324_1879444239_n.jpg
188 ms
1461686_214878632026902_874415194_n.jpg
184 ms
994031_206404419540990_1618372493_n.jpg
211 ms
jille.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
jille.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
jille.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jille.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 Jille.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.
jille.jp
Open Graph description is not detected on the main page of JILLE. 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: