6.3 sec in total
891 ms
4.7 sec
675 ms
Welcome to foodison.jp homepage info - get ready to check Foodison best content for Japan right away, or after learning these important things about foodison.jp
飲食店向けの水産品EC「魚ポチ」、いつも新しい街の魚屋「sakana bacca」、フード業界に特化した人材紹介サービス「フード人材バンク」を運営する、生鮮流通をテクノロジーを使いアップデートするフーディソンのコーポレートサイト。
Visit foodison.jpWe analyzed Foodison.jp page load time and found that the first response time was 891 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
foodison.jp performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value5.0 s
27/100
25%
Value11.4 s
5/100
10%
Value720 ms
41/100
30%
Value0.189
65/100
15%
Value14.7 s
8/100
10%
891 ms
174 ms
199 ms
315 ms
838 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 51% of them (50 requests) were addressed to the original Foodison.jp, 10% (10 requests) were made to Use.typekit.net and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Foodison.jp.
Page size can be reduced by 537.5 kB (11%)
5.1 MB
4.5 MB
In fact, the total size of Foodison.jp main page is 5.1 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. 65% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 265.7 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 265.7 kB or 61% of the original size.
Potential reduce by 63.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. Foodison images are well optimized though.
Potential reduce by 176.6 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 176.6 kB or 56% of the original size.
Potential reduce by 31.6 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. Foodison.jp needs all CSS files to be minified and compressed as it can save up to 31.6 kB or 82% of the original size.
Number of requests can be reduced by 41 (48%)
86
45
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foodison. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
foodison.jp
891 ms
style.css
174 ms
bju2gos.js
199 ms
styles.css
315 ms
foodison.jp
838 ms
jquery.js
486 ms
jquery-migrate.min.js
323 ms
jquery.min.js
38 ms
jquery.min.js
49 ms
fontplus.js
510 ms
jquery.fullwidthslider.1.0.js
353 ms
bookmark_button.js
514 ms
platform.js
63 ms
jquery.form.min.js
341 ms
scripts.js
469 ms
wp-embed.min.js
483 ms
s_retargeting.js
580 ms
conversion.js
38 ms
foodison.jp
123 ms
wp-emoji-release.min.js
178 ms
sdk.js
467 ms
analytics.js
45 ms
button-only@2x.png
424 ms
logo.png
425 ms
replatform.jpg
1563 ms
banner6.jpg
1529 ms
sakana_bacca_banner.jpg
1398 ms
banner5.jpg
1408 ms
banner1.jpg
1588 ms
banner3.jpg
2123 ms
mission.png
1573 ms
read_more.png
1570 ms
vision_01.png
1689 ms
read_more_black.png
1723 ms
top_button.png
1741 ms
message_from.png
1729 ms
tanaka.jpg
2002 ms
senoo.jpg
2073 ms
ishii.jpg
1887 ms
yamada.jpg
2072 ms
kitaura.jpg
2072 ms
yamamoto.jpg
2073 ms
watanabe_a.jpg
2369 ms
kotani.jpg
2352 ms
yosuke.jpg
2364 ms
sakamoto.jpg
2374 ms
nagakawa.jpg
2529 ms
kimutaku.jpg
2403 ms
takahiro.jpg
2684 ms
TypeA_blue.jpg
2542 ms
info_facebook.png
2555 ms
info_mail.png
2546 ms
info_tel.png
2591 ms
line88x20.png
2706 ms
search.png
2692 ms
arrow.png
2703 ms
back_white.png
2715 ms
origin.jpg
2931 ms
message.jpg
2836 ms
collect
219 ms
5OUVYRRl-m_VGFgU5Bzh1Ju-Co28Kx_kR5bGaSgtJZtff5A5gsMmeMJ6Mk6f5Mb.woff
219 ms
P4pCxFXhYd38XuNKc3hZ-kdsyzx6rNLMVc6jlKi3Zvqff555gsMmeMJ6Mk6f5MS.woff
301 ms
FzeHHadEyVLoGyme8_fSevvHRf79Tv0tzXk9Bm1xzNJff51YggMmeMJ6Mk6f5MS.woff
457 ms
D-FAzNsA0DfUbqs9jWUE2_sgKrMAJztzrviPL4_WBHjffV2YggMmeMJ6Mk6f5Mb.woff
541 ms
widgets.js
203 ms
280 ms
mkfont
1606 ms
collect
569 ms
238 ms
rx_J9Mj_l7eMe0dycJ0a_0PM_xYxD1ozUG7nHYSjk9JffFE5gsMmeMJ6Mk6f5Mt.woff
320 ms
lRiU-4KJ-o7i0qeKU2vGAEcdF4kNIjqeeeNlatJ1omJff5P5gsMmeMJ6Mk6f5gI.woff
319 ms
p3GaJQ-0QU3TSzpHiZkZR5wm3mqSOWolYsoVhlhE63Mff5zYggMmeMJ6Mk6f5Mt.woff
491 ms
R594Cad-XZIM03oMALzg_G3rXr5B2OSh7k6zc-WsbOIff5nYggMmeMJ6Mk6f5gI.woff
560 ms
sijosaiko_back2.png
2451 ms
481 ms
3d4c80e6
500 ms
cb=gapi.loaded_0
165 ms
cb=gapi.loaded_1
166 ms
fastbutton
330 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
311 ms
417 ms
reset.css
240 ms
entry-button.css
257 ms
xd_arbiter.php
379 ms
xd_arbiter.php
582 ms
postmessageRelay
225 ms
p.gif
299 ms
cb=gapi.loaded_0
90 ms
cb=gapi.loaded_1
89 ms
button-counter.gif
70 ms
ga-audiences
148 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
81 ms
3193398744-postmessagerelay.js
79 ms
rpc:shindig_random.js
77 ms
cb=gapi.loaded_0
11 ms
jot
92 ms
sijosaiko_back.png
1481 ms
bg.png
1499 ms
wDfDROLQAAAA==
2 ms
foodison.jp 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
foodison.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
foodison.jp 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 Foodison.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 Foodison.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.
foodison.jp
Open Graph data is detected on the main page of Foodison. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: