7.1 sec in total
531 ms
6.1 sec
520 ms
Click here to check amazing Appleple content for Japan. Otherwise, check out these important facts you probably never knew about appleple.com
Web制作、CMS構築なら名古屋のアップルップルへ。CMSを使ったWebサイトの更新など、お客様のインターネット活用をサポートいたします。お気軽にご相談ください。
Visit appleple.comWe analyzed Appleple.com page load time and found that the first response time was 531 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
appleple.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value10.6 s
0/100
25%
Value8.7 s
17/100
10%
Value1,440 ms
15/100
30%
Value0.001
100/100
15%
Value11.5 s
18/100
10%
531 ms
951 ms
162 ms
938 ms
948 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 65% of them (51 requests) were addressed to the original Appleple.com, 13% (10 requests) were made to Facebook.com and 4% (3 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Appleple.com.
Page size can be reduced by 791.2 kB (29%)
2.7 MB
1.9 MB
In fact, the total size of Appleple.com main page is 2.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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 43.2 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 43.2 kB or 81% of the original size.
Potential reduce by 92.3 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. Appleple images are well optimized though.
Potential reduce by 342.9 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 342.9 kB or 69% of the original size.
Potential reduce by 312.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. Appleple.com needs all CSS files to be minified and compressed as it can save up to 312.8 kB or 86% of the original size.
Number of requests can be reduced by 23 (31%)
74
51
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Appleple. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
appleple.com
531 ms
www.appleple.com
951 ms
reset.css
162 ms
acms-admin.min.css
938 ms
acms.css
948 ms
flexslider.css
323 ms
appleple2014.css
897 ms
js
64 ms
jquery.js
1512 ms
acms.js
2210 ms
common.js
481 ms
137ea378-8de9-4d36-827c-fe4e4287b03e.js
124 ms
jquery.flexslider-min.js
801 ms
top2014.js
971 ms
gmap.js
1056 ms
facebook.js
1081 ms
index.js
360 ms
woopra.v2.js
87 ms
underscore-min.js
232 ms
config.js
507 ms
ga.js
23 ms
j.php
23 ms
btn_detail01.png
223 ms
3e140744b57d7c2f11eaf7e315869ae0.jpg
1088 ms
5446367eb6209.png
779 ms
52b27cda1f9ce.jpg
671 ms
tiny-4bc2ecfe2bf27e9573bc3ba32baf065b.png
793 ms
tiny-55554b773e7e2.png
1134 ms
tiny-b0904c1bef112338772e422d9d254045.png
1162 ms
tiny-13f4789a01c843b3f22bca0832a9fb35.png
1009 ms
tiny-545b0a68bc5f0.png
1096 ms
tiny-54463ddda75e5.png
1597 ms
tiny-53ba269bd7a50.jpg
1178 ms
tiny-538e7cfa7bf8b.png
1635 ms
tiny-53435f1f732e6.png
1409 ms
6f29ff0a1cbb5790ad5482766207db4b.png
1293 ms
83dc50a72b7287682b6df34341cb37e6.jpg
1330 ms
8f110916c0023c5ffeb8d89f7a58f4de.jpg
1345 ms
iconFb.png
1448 ms
tiny-5361d64f1eda9.png
1498 ms
tiny-5361d72d05a5a.png
1514 ms
tiny-5361d715ecc63.png
1564 ms
b99525d4dc0338baac4ee97c10acb82b.gif
1606 ms
880a27bc9cabb8ccce2e92b2fb4b1d73.gif
1666 ms
e2d5ad0cfd8a54d55180173d1e496539.gif
1683 ms
98c8125420c6af510d3255acbf823b53.gif
1721 ms
516fad774eec7.jpg
1755 ms
a0bbac22c88835bc3cae56ad935a8d8f.png
1760 ms
516fad77515c1.jpg
1815 ms
btn_search_black.png
1833 ms
all.js
87 ms
sitelogo5.svg
1835 ms
btn_search.png
1860 ms
bg_slide.jpg
1901 ms
220x220.png
1900 ms
__utm.gif
50 ms
v.gif
46 ms
123 ms
uh.js
557 ms
111 ms
btn_slide_left.png
1783 ms
btn_slide_right.png
1786 ms
xd_arbiter.php
61 ms
xd_arbiter.php
178 ms
2656a5f2-9367-4d1d-af19-8cd9f9028d08.eot
58 ms
01ab709f-22cf-4831-b24a-8cf4eb852687.eot
145 ms
30cb567e-f796-469c-8fae-9d23c9be0e88.eot
143 ms
like.php
96 ms
like.php
155 ms
like.php
138 ms
like.php
143 ms
like.php
160 ms
like.php
149 ms
wy1X4hBW7e7.js
173 ms
LVx-xkvaJ0b.png
185 ms
like.php
90 ms
like.php
112 ms
like.php
103 ms
jquery-ui.min.js
1860 ms
appleple.com accessibility score
appleple.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
appleple.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Appleple.com 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 Appleple.com 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.
appleple.com
Open Graph data is detected on the main page of Appleple. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: