Tools & Wizards About Us
ailedore.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ailedore.co.jp

札幌ケーキ店「欧風洋菓子 エル・ドール」｜公式サイト

Page Load Speed

5.1 sec in total

First Response

879 ms

Resources Loaded

3.9 sec

Page Rendered

240 ms

ailedore.co.jp screenshot

About Website

Visit ailedore.co.jp now to see the best up-to-date Ailedore content and also check out these interesting facts you probably never knew about ailedore.co.jp

札幌のケーキ店「欧風洋菓子 エル・ドール」の公式サイトです。オンラインケーキ予約や宅配サービスも行っています。

Visit ailedore.co.jp

Key Findings

We analyzed Ailedore.co.jp page load time and found that the first response time was 879 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

ailedore.co.jp performance score

0

Network Requests Diagram

ailedore.co.jp

879 ms

import.css

332 ms

jquery.min.js

5 ms

smoothScroll.js

337 ms

slider.css

338 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 68% of them (41 requests) were addressed to the original Ailedore.co.jp, 5% (3 requests) were made to Platform.twitter.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Ailedore.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 454.8 kB (33%)

Content Size

1.4 MB

After Optimization

943.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ailedore.co.jp main page is 1.4 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 768.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 20.9 kB

  • Original 27.9 kB
  • After minification 23.9 kB
  • After compression 6.9 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 4.0 kB, which is 14% 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 20.9 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 5.2 kB

  • Original 768.6 kB
  • After minification 763.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. Ailedore images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 201.3 kB

  • Original 327.7 kB
  • After minification 326.0 kB
  • After compression 126.4 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 201.3 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 227.4 kB

  • Original 274.3 kB
  • After minification 265.7 kB
  • After compression 46.9 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. Ailedore.co.jp needs all CSS files to be minified and compressed as it can save up to 227.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (30%)

Requests Now

57

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ailedore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ailedore.co.jp

ailedore.co.jp

879 ms

import.css

import.css

332 ms

jquery.min.js

jquery.min.js

5 ms

smoothScroll.js

smoothScroll.js

337 ms

slider.css

slider.css

338 ms

slider.js

slider.js

1680 ms

rollover.js

rollover.js

356 ms

reset.css

reset.css

169 ms

style.css

style.css

356 ms

base.css

base.css

172 ms

contents.css

contents.css

174 ms

ga.js

ga.js

10 ms

img_01.jpg

img_01.jpg

839 ms

img_02.jpg

img_02.jpg

708 ms

img_03.jpg

img_03.jpg

866 ms

sogyosai1-150x150.png

sogyosai1-150x150.png

504 ms

top_img05.png

top_img05.png

191 ms

fatherroll1-150x150.png

fatherroll1-150x150.png

372 ms

2015.6web1-150x150.png

2015.6web1-150x150.png

725 ms

footer_img01.jpg

footer_img01.jpg

538 ms

footer_img02.jpg

footer_img02.jpg

671 ms

footer_img03.jpg

footer_img03.jpg

717 ms

all.js

all.js

61 ms

header_logo.jpg

header_logo.jpg

836 ms

header_nav01.jpg

header_nav01.jpg

878 ms

header_nav02.jpg

header_nav02.jpg

890 ms

widgets.js

widgets.js

98 ms

header_tel.jpg

header_tel.jpg

841 ms

gnav.jpg

gnav.jpg

942 ms

loader2.gif

loader2.gif

945 ms

loader.gif

loader.gif

968 ms

top_tit01.jpg

top_tit01.jpg

997 ms

top_img06.jpg

top_img06.jpg

1009 ms

top_img08.jpg

top_img08.jpg

1194 ms

top_img09.jpg

top_img09.jpg

1109 ms

top_img10.jpg

top_img10.jpg

1111 ms

top_img11.jpg

top_img11.jpg

1137 ms

top_img12.jpg

top_img12.jpg

1348 ms

top_img13.jpg

top_img13.jpg

1186 ms

side_bnr_event.jpg

side_bnr_event.jpg

1276 ms

top_img16.jpg

top_img16.jpg

1278 ms

top_img15.jpg

top_img15.jpg

1303 ms

top_img18.jpg

top_img18.jpg

1363 ms

top_img17.jpg

top_img17.jpg

1371 ms

footer_logo.jpg

footer_logo.jpg

1444 ms

oEom5vutmII

oEom5vutmII

106 ms

__utm.gif

__utm.gif

28 ms

147 ms

xd_arbiter.php

xd_arbiter.php

24 ms

xd_arbiter.php

xd_arbiter.php

32 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

257 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

33 ms

www-embed-player.js

www-embed-player.js

59 ms

base.js

base.js

91 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

50 ms

ad_status.js

ad_status.js

48 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

38 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

41 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

65 ms

jot

jot

80 ms

SEO Factors

ailedore.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ailedore.co.jp 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 Ailedore.co.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.

Social Sharing Optimization

ailedore.co.jp

Open Graph description is not detected on the main page of Ailedore. 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: