16 sec in total
1.1 sec
14.5 sec
410 ms
Visit orandaya.net now to see the best up-to-date Orandaya content for Japan and also check out these interesting facts you probably never knew about orandaya.net
オランダ家では、千葉県の安全・安心・おいしい素材を利用した本当のおいしさを届けます。
Visit orandaya.netWe analyzed Orandaya.net page load time and found that the first response time was 1.1 sec and then it took 14.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
orandaya.net performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value33.8 s
0/100
25%
Value21.2 s
0/100
10%
Value390 ms
68/100
30%
Value0.452
20/100
15%
Value12.0 s
16/100
10%
1124 ms
1151 ms
2537 ms
400 ms
415 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 95% of them (42 requests) were addressed to the original Orandaya.net, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (11.1 sec) belongs to the original domain Orandaya.net.
Page size can be reduced by 700.0 kB (28%)
2.5 MB
1.8 MB
In fact, the total size of Orandaya.net main page is 2.5 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. 25% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 17.6 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 17.6 kB or 74% of the original size.
Potential reduce by 341.5 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. Obviously, Orandaya needs image optimization as it can save up to 341.5 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 277.2 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 277.2 kB or 69% of the original size.
Potential reduce by 63.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. Orandaya.net needs all CSS files to be minified and compressed as it can save up to 63.8 kB or 88% of the original size.
Number of requests can be reduced by 21 (49%)
43
22
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orandaya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
orandaya.net
1124 ms
style.css
1151 ms
jquery.js
2537 ms
jquery.page-scroller.js
400 ms
smartrollover.js
415 ms
heightLine.js
624 ms
jquery.carouFredSel-6.1.0.js
1345 ms
common.js
593 ms
styles.css
613 ms
jquery.js
1865 ms
jquery-migrate.min.js
1011 ms
jquery.jscrollpane.min.js
845 ms
jquery.mousewheel.js
1028 ms
top.js
1048 ms
jquery.form.min.js
966 ms
scripts.js
1040 ms
wp-emoji-release.min.js
575 ms
analytics.js
144 ms
h_bg.png
11074 ms
h_arrow.png
405 ms
sp_menu.gif
195 ms
h_logo.png
576 ms
web.png
201 ms
h_link02.png
389 ms
g_navi01_out.png
402 ms
g_navi02_out.png
583 ms
g_navi03_out.png
602 ms
g_navi04_out.png
607 ms
g_navi05_out.png
745 ms
g_navi06_out.png
757 ms
g_navi07_out.png
774 ms
orandaya_top1005A2.jpg
3966 ms
orandaya_top_rakkasei.jpg
3832 ms
ichigoB.jpg
3100 ms
main_bg.png
932 ms
egao_banner.jpg
3296 ms
top25cake1027.jpg
2256 ms
gift4.jpg
2825 ms
news_title.png
3017 ms
news_bg.jpg
3396 ms
line01.gif
3290 ms
f_bg.png
3673 ms
icon01.png
3487 ms
collect
23 ms
orandaya.net 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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
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.
orandaya.net 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
orandaya.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orandaya.net 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 Orandaya.net 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.
orandaya.net
Open Graph description is not detected on the main page of Orandaya. 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: