6.6 sec in total
673 ms
5.4 sec
561 ms
Welcome to ap-story.jp homepage info - get ready to check Ap Story best content for Japan right away, or after learning these important things about ap-story.jp
人気ブランドアプワイザー・リッシェ、オンもオフも輝きたい女性に向けたジャスグリッティー、大人カジュアルスタイルリランドチュール、繊細で柔軟な軸のある女性への、ワードローブを提案マイストラーダの直営ファッション通販サイト【Arpege story】
Visit ap-story.jpWe analyzed Ap-story.jp page load time and found that the first response time was 673 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ap-story.jp performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value14.1 s
0/100
25%
Value11.2 s
5/100
10%
Value590 ms
51/100
30%
Value0.694
7/100
15%
Value21.3 s
1/100
10%
673 ms
37 ms
58 ms
459 ms
10 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 62% of them (99 requests) were addressed to the original Ap-story.jp, 21% (34 requests) were made to Ap-storyjp.s3.amazonaws.com and 4% (6 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Ap-storyjp.s3.amazonaws.com.
Page size can be reduced by 467.9 kB (9%)
5.3 MB
4.8 MB
In fact, the total size of Ap-story.jp main page is 5.3 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. 70% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 81.3 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 12.5 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 81.3 kB or 84% of the original size.
Potential reduce by 57.1 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. Ap Story images are well optimized though.
Potential reduce by 268.7 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 268.7 kB or 70% of the original size.
Potential reduce by 60.8 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. Ap-story.jp needs all CSS files to be minified and compressed as it can save up to 60.8 kB or 84% of the original size.
Number of requests can be reduced by 46 (30%)
155
109
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ap Story. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
ap-story.jp
673 ms
jquery.min.js
37 ms
jquery-ui.min.js
58 ms
jquery-ui-1.10.3.custom.css
459 ms
underscore-min.js
10 ms
underscore.string.min.js
11 ms
json2.js
13 ms
moment.min.js
13 ms
numeral.min.js
9 ms
backbone-min.js
12 ms
jquery-ui-i18n.js
637 ms
jquery.form.js
638 ms
namespace.js
333 ms
console.js
338 ms
resource.js
472 ms
util.js
500 ms
promotion.js
507 ms
bootstrap.js
608 ms
app.js
625 ms
mem.js
670 ms
rollover.js
675 ms
heightLine.js
762 ms
smoothscroll.js
784 ms
jquery.cookie.js
795 ms
jquery.side.js
796 ms
jquery.header.js
835 ms
jquery.header.menu.js
843 ms
jquery.tile.js
915 ms
common.css
944 ms
layout.css
955 ms
header.css
956 ms
footer.css
1002 ms
css
44 ms
jquery.carouFredSel-6.2.1-packed.js
1347 ms
jquery.home.js
1069 ms
jquery.lazyload.js
1104 ms
page-home.css
1115 ms
conversion.js
17 ms
conversion.js
584 ms
s_retargeting.js
540 ms
analytics.js
21 ms
h1.gif
534 ms
header_form_details.gif
164 ms
btn_close.png
156 ms
header_sub_menu_title_1.png
171 ms
header_sub_menu_title_2.png
164 ms
header_sub_menu_title_8.png
175 ms
header_sub_menu_title_3.png
165 ms
header_sub_menu_title_6.png
309 ms
header_sub_menu_title_4.png
322 ms
header_sub_menu_title_5.png
323 ms
magazine_new.gif
322 ms
btn_banner_all.gif
334 ms
spacer.gif
338 ms
h2_news.png
461 ms
news_arrow_l.png
480 ms
news_arrow_r.png
482 ms
btn_pagetop.gif
482 ms
footer_logo.gif
500 ms
btn_insta.gif
507 ms
btn_facebook.gif
615 ms
btn_twitter.gif
641 ms
btn_line.png
641 ms
footer_banner_1.jpg
799 ms
footer_banner_2.jpg
665 ms
footer_banner_3.jpg
841 ms
bnr_20160226212412768.jpg
1182 ms
bnr_20160226213907578.jpg
937 ms
bnr_20160227144745394.jpg
1094 ms
bnr_20160222215921180.jpg
1172 ms
bnr_20160229192403662.jpg
1031 ms
bnr_20160222220441868.jpg
1353 ms
bnr_20160222220641058.jpg
1650 ms
bnr_20160301061557776.jpg
1378 ms
bnr_20160227143934570.jpg
1770 ms
bnr_20160226215752567.jpg
1682 ms
bnr_20160222220108720.jpg
1696 ms
bnr_20160222215711504.jpg
1853 ms
bnr_20160222215322507.jpg
1898 ms
bnr_20160222215128701.jpg
2291 ms
bnr_20160222215512700.jpg
2208 ms
bnr_20160222214620015.jpg
2209 ms
bnr_20160222214838008.jpg
2280 ms
bnr_20160222214312900.jpg
2359 ms
bnr_20160222214101023.jpg
2413 ms
bnr_20160222213332085.jpg
2737 ms
bnr_20160222213754687.jpg
2778 ms
bnr_20160222211709756.jpg
2957 ms
bnr_20160222212434274.jpg
2966 ms
bnr_20160222212743975.jpg
3192 ms
bnr_20160222213056615.jpg
2926 ms
bnr_20160213174148566.jpg
3087 ms
bnr_20160227144211100.jpg
2959 ms
bnr_20160226215854966.jpg
3103 ms
bnr_20160227145050828.jpg
3128 ms
header_icon_1.gif
756 ms
collect
25 ms
header_icon_2.gif
766 ms
header_icon_3.gif
766 ms
header_form_search.gif
792 ms
header_form_bg.gif
879 ms
header_icon_cart.gif
915 ms
header_brand_1.gif
910 ms
header_brand_2.gif
910 ms
header_brand_3.gif
948 ms
header_brand_4.gif
959 ms
header_brand_5.gif
1023 ms
header_menu_1.png
1070 ms
collect
60 ms
fbevents.js
89 ms
28 ms
conversion.js
591 ms
47 ms
ga-audiences
48 ms
header_menu_2.png
975 ms
header_menu_3.png
969 ms
header_menu_4.png
1008 ms
header_menu_5.png
1020 ms
header_menu_6.png
1064 ms
header_menu_7.png
1114 ms
header_menu_8.png
980 ms
header_menu_9.png
968 ms
header_menu_10.png
1017 ms
header_sub_menu_bg.png
1032 ms
h2_newitems.gif
1055 ms
list_all_l.gif
1109 ms
list_all_r.gif
987 ms
h2_ranking.gif
969 ms
h2_coordinate.gif
1023 ms
h2_staffstyling.gif
1041 ms
853 ms
select
964 ms
select
876 ms
select
903 ms
select
911 ms
arr_l.gif
933 ms
arr_r.gif
952 ms
bnr_20160226212610258.jpg
2428 ms
bnr_20160226214945774.jpg
2413 ms
bnr_20160227154224430.jpg
2538 ms
header_sub_menu_line.png
1001 ms
01_001.jpg
471 ms
list_icon_reserve.gif
162 ms
list_icon_magazine.gif
163 ms
list_icon_new.gif
208 ms
spacer.gif
1994 ms
01_001.jpg
482 ms
01_001.jpg
500 ms
01_001.jpg
513 ms
01_001.jpg
506 ms
rank_01.png
216 ms
rank_02.png
204 ms
rank_03.png
285 ms
rank_04.png
307 ms
rank_05.png
307 ms
list_icon_reserve.png
355 ms
list_icon_rearrival.gif
352 ms
list_icon_magazine.png
380 ms
header_sub_menu_line_sub2.png
393 ms
ap-story.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
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.
ap-story.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
Page has valid source maps
ap-story.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 Ap-story.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 Ap-story.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.
ap-story.jp
Open Graph description is not detected on the main page of Ap Story. 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: