11 sec in total
756 ms
9.8 sec
407 ms
Welcome to veggy.jp homepage info - get ready to check Veggy best content for Japan right away, or after learning these important things about veggy.jp
Veggy Online
Visit veggy.jpWe analyzed Veggy.jp page load time and found that the first response time was 756 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
veggy.jp performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value23.9 s
0/100
25%
Value13.3 s
2/100
10%
Value560 ms
52/100
30%
Value0.024
100/100
15%
Value20.3 s
2/100
10%
756 ms
324 ms
330 ms
333 ms
353 ms
Our browser made a total of 174 requests to load all elements on the main page. We found that 55% of them (95 requests) were addressed to the original Veggy.jp, 11% (20 requests) were made to Static.xx.fbcdn.net and 8% (14 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Veggy.jp.
Page size can be reduced by 1.3 MB (25%)
5.2 MB
3.9 MB
In fact, the total size of Veggy.jp main page is 5.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 39.1 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 19.5 kB, which is 43% 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 39.1 kB or 86% of the original size.
Potential reduce by 235.2 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. Veggy images are well optimized though.
Potential reduce by 767.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 767.9 kB or 69% of the original size.
Potential reduce by 247.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. Veggy.jp needs all CSS files to be minified and compressed as it can save up to 247.6 kB or 83% of the original size.
Number of requests can be reduced by 49 (29%)
169
120
The browser has sent 169 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Veggy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
veggy.jp
756 ms
reset.css
324 ms
style.css
330 ms
common.css
333 ms
layout.css
353 ms
jquery.bxslider.css
359 ms
magazine.css
464 ms
anythingslider.css
664 ms
editor.css
657 ms
jquery-1.9.1.min.js
1156 ms
magazine.js
657 ms
jquery.easing.1.3.js
664 ms
jquery.bxslider.js
931 ms
jquery.anythingslider.min.js
1146 ms
analytics.js
86 ms
TlEVO1fNTyo
157 ms
tl4S0kgU2Vo
194 ms
header-logo.png
526 ms
global-nav01.png
502 ms
global-nav02.png
494 ms
global-nav03.png
497 ms
serchbox-bg.png
496 ms
btn_search.png
494 ms
whatsveggy.png
1094 ms
nav01.png
925 ms
nav02.png
924 ms
nav03.png
926 ms
nav04.png
1043 ms
nav05.png
1045 ms
nav06.png
1224 ms
nav07.png
1344 ms
nav08.png
1345 ms
01.png
2663 ms
02.png
2719 ms
03.png
2906 ms
04.png
3038 ms
05.png
2507 ms
06.png
2908 ms
07.png
4468 ms
headline.png
3005 ms
headline-bg.png
3055 ms
arrow03.png
3233 ms
8d3f74a7d00ba129765fc52f73097201.jpg
3749 ms
be27c2703992de7f97a5a9aaf6db9691.jpg
3988 ms
a75bf5886dce6efdcc8803441712a5a8.jpg
3656 ms
fb0d14eac6ab2805a684af7c9b3217c8.jpg
3971 ms
da77beeff38eeb5fcde9ad818b7ad287.jpg
4105 ms
30a0ff49846e9d1cfecf4b0abaead122.jpg
4572 ms
topveggy.jpg
4744 ms
fb-plugin-tit.png
4323 ms
ba7b30257b306d54277fae69168a532c.jpg
5962 ms
facebook.png
4434 ms
embed
189 ms
twitter.png
4609 ms
likebox.php
436 ms
collect
18 ms
www-embed-player-vflfNyN_r.css
70 ms
www-embed-player.js
102 ms
base.js
207 ms
js
265 ms
init_embed.js
317 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
68 ms
ad_status.js
141 ms
hDvwL1_H7g-.css
114 ms
56WNbrUYLbL.css
125 ms
yZ--Yu0PDbV.css
132 ms
QD6_ejUFoCN.css
143 ms
xxJgcoj8mOR.css
131 ms
1kPfZUdGrka.js
154 ms
Yuj_Y8xNH2C.js
188 ms
Mpe38fuBVZ2.js
200 ms
n8qIhCw3vMx.js
204 ms
QKy94bWvcbp.js
200 ms
6q5od22S-uf.js
206 ms
7B-2ZS3Qt8r.js
264 ms
qcMicXoOToy.js
271 ms
57RpJa05x58.js
269 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
106 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
113 ms
veggybooks.png
4420 ms
773a34b5a1ce04e4a14bd9b00e0e6f18.jpg
4645 ms
243948a22385e78eebc9047f47c28264.jpg
4725 ms
7cea1714a03bfffb1adce1fa9d28ec01.jpg
4674 ms
940ae113d53ca1d6560b38b4adb25829.jpg
4846 ms
43bb9fc5ad1edb3a039f80f01f41577a.jpg
5198 ms
common.js
220 ms
map.js
220 ms
google4.png
177 ms
overlay.js
175 ms
12802955_1064836196913726_9054590686246060054_n.jpg
296 ms
safe_image.php
367 ms
12801144_1064832406914105_8736779373654260897_n.jpg
348 ms
535207_1072526192811393_3225941874562899917_n.jpg
360 ms
12196296_1072528486144497_4129651506532230384_n.jpg
348 ms
10325785_1072529009477778_7379020438548389985_n.jpg
360 ms
12239538_255724764769778_185497823226015194_n.jpg
369 ms
922686_1064176643646348_3320960966803437391_n.jpg
358 ms
safe_image.php
370 ms
wL6VQj7Ab77.png
233 ms
s7jcwEQH7Sx.png
231 ms
QDwYpIaRyfG.png
231 ms
K00K-UgnsKu.png
231 ms
util.js
275 ms
onion.js
274 ms
search_impl.js
353 ms
fa11df457889b323f09ab4fde84e6890.jpg
4825 ms
c40b68c4dc0c23fb89a18a6e1808a8ad.jpg
5010 ms
stats.js
171 ms
moon22.png
4507 ms
moon23.png
4647 ms
moon24.png
4835 ms
ViewportInfoService.GetViewportInfo
165 ms
ViewportInfoService.GetViewportInfo
158 ms
transparent.png
108 ms
kh
170 ms
kh
170 ms
moon25.png
4895 ms
VXcANLwwL5J.js
56 ms
AmlxWlqMvlv.js
54 ms
controls.js
35 ms
moon26.png
4807 ms
ViewportInfoService.GetViewportInfo
62 ms
css
99 ms
entity11.png
30 ms
moon27.png
4724 ms
moon28.png
4843 ms
vt
164 ms
vt
174 ms
mapcnt6.png
44 ms
vt
125 ms
vt
114 ms
vt
118 ms
vt
121 ms
vt
189 ms
vt
185 ms
vt
182 ms
vt
201 ms
vt
205 ms
tmapctrl.png
26 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
4 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
8 ms
AuthenticationService.Authenticate
14 ms
moon29.png
3783 ms
moon0.png
3616 ms
moon1.png
3610 ms
moon2.png
3471 ms
moon3.png
3465 ms
moon4.png
3534 ms
moon5.png
3561 ms
moon6.png
3554 ms
moon7.png
3400 ms
moon8.png
3021 ms
moon9.png
2977 ms
moon10.png
2873 ms
moon11.png
2913 ms
moon12.png
2829 ms
moon13.png
2635 ms
moon14.png
2549 ms
moon15.png
2598 ms
moon16.png
2602 ms
moon17.png
2555 ms
moon18.png
2526 ms
moon19.png
2382 ms
moon20.png
2183 ms
moon21.png
2251 ms
6a1da716bd26a9a001a2c7b823a2e0ce.jpg
2619 ms
0a7839f1ac5de456560b5ef4692983d5.jpg
2503 ms
7cc28c63bd4606fcab499507fd1d6c71.jpg
2362 ms
8a6a3268c0bf46e687edbac6d15eea78.jpg
2286 ms
pagetop.png
1948 ms
footer-logo.png
2009 ms
arrow02.png
2118 ms
QuotaService.RecordEvent
13 ms
collect
4 ms
veggy.jp 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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
veggy.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
veggy.jp SEO score
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 Veggy.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 Veggy.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.
veggy.jp
Open Graph description is not detected on the main page of Veggy. 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: