32.1 sec in total
4.7 sec
26.6 sec
793 ms
Welcome to sou-recipe.com homepage info - get ready to check Sou Recipe best content for Japan right away, or after learning these important things about sou-recipe.com
プロのレシピを全て公開するブログ。レストランでのレシピ、作り方をたくさんの写真を使って詳しく公開! ”ちゃんとつくる。ちゃんとたべる。”
Visit sou-recipe.comWe analyzed Sou-recipe.com page load time and found that the first response time was 4.7 sec and then it took 27.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
sou-recipe.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value13.3 s
0/100
25%
Value30.7 s
0/100
10%
Value38,070 ms
0/100
30%
Value0.037
100/100
15%
Value52.0 s
0/100
10%
4701 ms
483 ms
438 ms
439 ms
633 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 56% of them (71 requests) were addressed to the original Sou-recipe.com, 7% (9 requests) were made to Apis.google.com and 6% (7 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Go2web20.net.
Page size can be reduced by 290.4 kB (32%)
919.3 kB
628.9 kB
In fact, the total size of Sou-recipe.com main page is 919.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. 55% of websites need less resources to load. Images take 458.3 kB which makes up the majority of the site volume.
Potential reduce by 61.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 61.2 kB or 78% of the original size.
Potential reduce by 2.6 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. Sou Recipe images are well optimized though.
Potential reduce by 152.0 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 152.0 kB or 52% of the original size.
Potential reduce by 74.7 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. Sou-recipe.com needs all CSS files to be minified and compressed as it can save up to 74.7 kB or 85% of the original size.
Number of requests can be reduced by 50 (41%)
122
72
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sou Recipe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
sou-recipe.com
4701 ms
language-selector.css,qv=3.3.6.pagespeed.ce.XD4w0GZUwA.css
483 ms
common.css.pagespeed.ce.m0FC3aptKn.css
438 ms
layout.css.pagespeed.ce.1Vyr70keDu.css
439 ms
design.css.pagespeed.ce.4igloin4dt.css
633 ms
mobile.css.pagespeed.ce.B7ZTME9Esd.css
458 ms
mobile_layout.css.pagespeed.ce.lbLFKRh61u.css
459 ms
advanced.css.pagespeed.ce.HdFi4lSKe6.css
637 ms
style.css,qver=1.2.8.pagespeed.ce.iHhD_cqMHd.css
660 ms
wpp.css,qver=3.3.3.pagespeed.ce.ZUwz9rjzGg.css
661 ms
jquery.js,qver=1.11.2.pagespeed.jm.0kUhGt7Mm3.js
1444 ms
jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js
877 ms
adsbygoogle.js
115 ms
wp-emoji-release.min.js
2241 ms
line-button.js
644 ms
socialButton.js
457 ms
badge.js
20222 ms
analytics.js
78 ms
IMG_0243-150x150.jpg
495 ms
IMG_5877-150x150.jpg
822 ms
IMG_0823-150x150.jpg
898 ms
IMG_3660-150x150.jpg
435 ms
017-150x150.jpg
3107 ms
20100708020750cd8-150x150.jpg
946 ms
20100708020750fb0-150x150.jpg
966 ms
20110704011234bbb-150x150.jpg
1317 ms
20091107150553bc5-150x150.jpg
1390 ms
IMG_3712-150x150.jpg
1407 ms
IMG_7452-150x150.jpg
1246 ms
20090829002342b9c-150x150.jpg
1476 ms
2011040902351525d-150x150.jpg
1708 ms
20141006133930fe3-150x150.jpg
1627 ms
20140805155130468-150x150.jpg
1902 ms
201108091556556d4-150x150.jpg
2116 ms
IMG_4750-150x150.jpg
1951 ms
20100917010954cb8-150x150.jpg
1859 ms
20091107150510853-150x150.jpg
2784 ms
RIMG0148-150x150.jpg
2343 ms
200911210013066c9-150x150.jpg
2368 ms
026_20110720220540-150x150.jpg
2418 ms
IMG_6962-150x150.jpg
3451 ms
20100110015514b49-150x150.jpg
4113 ms
20110710002543f0c-150x150.jpg
3090 ms
20100331003606fd0-150x150.jpg
4361 ms
IMG_8137-150x150.jpg
4600 ms
Fricassee-150x150.jpg
4185 ms
ac42f65de47af5d6aca4efbb2208db321-150x150.jpg
4115 ms
sakana-150x150.png
4160 ms
RIMG0070_201402200013157ec-150x150.jpg
5013 ms
20130928015950ba1-150x150.jpg
4619 ms
Tiramisu-150x150.jpg
4608 ms
2011032522382586c-150x150.jpg
4969 ms
ca-pub-0889503789107774.js
266 ms
zrt_lookup.html
255 ms
show_ads_impl.js
157 ms
collect
80 ms
ads
228 ms
osd.js
107 ms
ads
426 ms
ads
787 ms
ads
423 ms
btn.js
174 ms
IMG_4236-150x150.jpg
5632 ms
ads
219 ms
IMG_7535-150x150.jpg
6851 ms
IMG_8006-150x150.jpg
4693 ms
abg.js
262 ms
m_js_controller.js
81 ms
20110203030945c4f-150x150.jpg
4314 ms
favicon
283 ms
s
298 ms
googlelogo_color_112x36dp.png
263 ms
mobile_unified_button_icon_white.png
56 ms
x_button_blue2.png
124 ms
imgad
148 ms
x1636-first_image-80x80.jpg.pagespeed.ic.0WN-WduAtS.jpg
4326 ms
x2316-first_image-80x80.jpg.pagespeed.ic.6c7NTXORZz.jpg
4321 ms
x698-first_image-80x80.jpg.pagespeed.ic.o4yqmzYldn.jpg
4417 ms
favicon
297 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
87 ms
x659-first_image-80x80.jpg.pagespeed.ic.Slp7GBPgUw.jpg
4156 ms
x632-first_image-80x80.jpg.pagespeed.ic.l4uzeDOU_w.jpg
4080 ms
x2007-first_image-80x80.jpg.pagespeed.ic.zVULmRN2u4.jpg
4084 ms
x552-first_image-80x80.jpg.pagespeed.ic.A1rUkWvJY4.jpg
4215 ms
80x80x7ed6eba46fd930df94bb57fb0b8d12a71-150x150.jpg.pagespeed.ic.3zSXc6QvB4.jpg
4226 ms
80x80xe80908076a46f20f26cdfe60c78742f81-150x150.jpg.pagespeed.ic.JOid4IHIkd.jpg
4188 ms
80x80x1cba7f8c7b9da1309a4bac9582f77ecb1-150x150.jpg.pagespeed.ic.SHu4CEmCJY.jpg
4094 ms
80x80x1d94ae962bee810309b7b2ba9240c3471-150x150.jpg.pagespeed.ic.2_YM6QS7IH.jpg
4163 ms
80x80x28934c46f3033b283e2bd529002b68ee1-150x150.jpg.pagespeed.ic.OvC_K8eyxD.jpg
4013 ms
en.png
3980 ms
xja.png.pagespeed.ic.-yBk9-mhsh.png
4004 ms
icon-arrow_r.png
4013 ms
activeview
66 ms
icon-arrow02.png
3785 ms
icon-arrow01.png
3801 ms
bg-pagetop.gif
3784 ms
print.css.pagespeed.ce.w3Bu_wD1_o.css
543 ms
sdk.js
199 ms
widgets.js
110 ms
button-only@2x.png
438 ms
bookmark_button.js
445 ms
platform.js
393 ms
button
86 ms
button
87 ms
button.css
286 ms
shared.js
271 ms
button.js
291 ms
263 ms
button.71000885400e222c3c0eec823f8f93f0.js
1358 ms
xd_arbiter.php
177 ms
xd_arbiter.php
405 ms
pocket_button.png
47 ms
cb=gapi.loaded_0
225 ms
cb=gapi.loaded_1
216 ms
fastbutton
291 ms
483 ms
postmessageRelay
175 ms
rs=AGLTcCMyLcvNMRO1OqsHIKvnNXauc5OVnQ
29 ms
cb=gapi.loaded_0
160 ms
cb=gapi.loaded_1
67 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
192 ms
1077434459-postmessagerelay.js
123 ms
rpc:shindig_random.js
65 ms
reset.css
39 ms
entry-button.css
39 ms
cb=gapi.loaded_0
27 ms
bbtn-s_v3.png
18 ms
sou-recipe.com 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
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
Links do not have a discernible name
sou-recipe.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
Browser errors were logged to the console
Page has valid source maps
sou-recipe.com 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sou-recipe.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 Sou-recipe.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.
sou-recipe.com
Open Graph description is not detected on the main page of Sou Recipe. 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: