6.5 sec in total
1.5 sec
4.7 sec
316 ms
Visit xoops.ec-cube.net now to see the best up-to-date Xoops EC CUBE content for India and also check out these interesting facts you probably never knew about xoops.ec-cube.net
独自性の高いECサイトが無料で手に入る、日本発ECオープンプラットフォーム「EC-CUBE」の開発コミュニティサイト
Visit xoops.ec-cube.netWe analyzed Xoops.ec-cube.net page load time and found that the first response time was 1.5 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
xoops.ec-cube.net performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.7 s
33/100
25%
Value8.0 s
21/100
10%
Value470 ms
61/100
30%
Value0.049
99/100
15%
Value11.0 s
21/100
10%
1470 ms
349 ms
359 ms
851 ms
785 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 55% of them (70 requests) were addressed to the original Xoops.ec-cube.net, 12% (15 requests) were made to Scontent-iad3-1.xx.fbcdn.net and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Xoops.ec-cube.net.
Page size can be reduced by 192.3 kB (32%)
595.8 kB
403.5 kB
In fact, the total size of Xoops.ec-cube.net main page is 595.8 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. 50% of websites need less resources to load. Images take 350.5 kB which makes up the majority of the site volume.
Potential reduce by 72.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. 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 72.1 kB or 81% of the original size.
Potential reduce by 36.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. Xoops EC CUBE images are well optimized though.
Potential reduce by 74.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 74.0 kB or 51% of the original size.
Potential reduce by 10.1 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. Xoops.ec-cube.net needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 83% of the original size.
Number of requests can be reduced by 55 (45%)
121
66
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xoops EC CUBE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
xoops.ec-cube.net
1470 ms
xoops.css
349 ms
styleNN.css
359 ms
AdLantisLoader.js
851 ms
xoops.js
785 ms
conversion.js
18 ms
style.css
523 ms
jsapi
43 ms
ojs
340 ms
bl_track.js
741 ms
logo.jpg
178 ms
copy.jpg
184 ms
bar.jpg
366 ms
login_top.gif
203 ms
_.gif
347 ms
login_user.gif
357 ms
login_pass.gif
373 ms
login_arrow.gif
377 ms
login_bottom.gif
399 ms
mainmenu_arrow.gif
515 ms
submenu_arrow.gif
529 ms
online_icon.gif
544 ms
online_top.gif
556 ms
online_line.gif
561 ms
online_bottom.gif
593 ms
bnr_design_213_top.jpg
1018 ms
title_left_top.gif
715 ms
title_right_top.gif
721 ms
title_left_bottom.gif
739 ms
title_right_bottom.gif
747 ms
welcom_top.gif
789 ms
welcom_image.gif
875 ms
welcom_bottom.gif
899 ms
guide.gif
923 ms
download_top.gif
1116 ms
xoops_paymant_cube3.jpg
1381 ms
xoops_cloud.jpg
1398 ms
kaihatsu_tsubo_s.png
1255 ms
kaihatsu_book_3.png
1472 ms
cavt49d38da8250e9.png
1184 ms
cavt4a37ee8fd51ea.jpg
1301 ms
cavt4cc77b246583a.png
1379 ms
cavt5614cbb81189e.png
1434 ms
cavt4e31f1d0dbbca.gif
1489 ms
cavt4fc892e845984.png
1547 ms
44 ms
cavt4c6f7172e3ccb.png
1559 ms
ga.js
28 ms
55 ms
__utm.gif
13 ms
ebis_tag.php
540 ms
18 ms
cavt56282c5e1453f.png
1571 ms
cavt49d3ff46ea4f5.jpg
1436 ms
cavt48abe00439cfb.png
1460 ms
cavt4d595311a74b1.png
1333 ms
cavt52835e010f1d3.png
1366 ms
cavt4a42356145b1d.gif
1413 ms
savt4511f780c4b6d.jpg
1425 ms
cavt4edae2b1297be.jpg
1470 ms
cavt4e0c4540cff5a.jpg
1651 ms
savt2a053.gif
1379 ms
cavt4f8e3980663f0.png
1391 ms
cavt45c7ccdca2d27.gif
1432 ms
cavt539811c93ddbd.png
1598 ms
cavt4c8d6ac5d0b11.png
1468 ms
cavt4d8496dac6976.gif
1468 ms
log.php
401 ms
15 ms
default+en.css
3 ms
default+en.I.js
7 ms
all.js
7 ms
ojs2
345 ms
133 ms
savt4511f9072c5ed.jpg
1375 ms
xd_arbiter.php
14 ms
xd_arbiter.php
26 ms
cavt5114c0badc00f.jpg
1447 ms
cavt546c5ff381015.png
1655 ms
cavt499213e0b2fa1.png
1671 ms
cavt5142853accd05.jpg
1439 ms
cavt4e1461132ec5c.png
1393 ms
savt451264bd656b7.gif
1432 ms
cavt528a0735ab19c.jpg
1441 ms
cavt4bd1186fb3295.png
1379 ms
385093.js
196 ms
bl_track.cgi
331 ms
blade_track_jp.js
348 ms
adlantis.www.js
166 ms
swfobject.js
329 ms
bl_track.cgi
337 ms
cavt4ee96d4d008cc.jpg
1326 ms
like_box.php
146 ms
bg.jpg
1325 ms
bar.jpg
1300 ms
siylcCr24Vv.css
15 ms
0q9EiyOzKa_.css
18 ms
_rx8naC75Dy.js
29 ms
x5F9OMjKyLw.js
45 ms
ICDbTSzjQEg.js
27 ms
TTCre3391I0.js
43 ms
title_bg.gif
1275 ms
12342763_1197274256952620_4960858713285929007_n.png
46 ms
164916_624126884267363_93143532_n.jpg
14 ms
1610918_364271917099118_662313968264276304_n.jpg
18 ms
11870660_833347206772447_6744769345077902582_n.jpg
17 ms
11698492_773885539396084_1742083658605887913_n.jpg
15 ms
10400127_975600175853266_9143455847714520623_n.jpg
16 ms
10547587_666571490091438_2368035492644075106_n.jpg
14 ms
12644954_668716466602863_3622403511235873131_n.jpg
15 ms
12729162_199463413747714_5406378448498023982_n.jpg
19 ms
12316666_10206777541230193_7733210623339644818_n.jpg
17 ms
10389123_590048484474076_577659727123384891_n.jpg
18 ms
165120_101350523273607_720458_n.jpg
19 ms
555465_304848766280435_1877680879_n.jpg
19 ms
10501873_255860397940383_7567236406870097517_n.jpg
17 ms
10940422_336119556585600_6494453365703296182_n.jpg
19 ms
wL6VQj7Ab77.png
10 ms
s7jcwEQH7Sx.png
11 ms
title_icon.gif
1185 ms
I6-MnjEovm5.js
4 ms
vlXaquuXMrr.js
5 ms
cookie_enabled_get.html
357 ms
bl_track.cgi
384 ms
Gfeeds
441 ms
Gfeeds
181 ms
__ptq.gif
22 ms
xoops.ec-cube.net accessibility score
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
xoops.ec-cube.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
xoops.ec-cube.net SEO score
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
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xoops.ec-cube.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 Xoops.ec-cube.net main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
xoops.ec-cube.net
Open Graph description is not detected on the main page of Xoops EC CUBE. 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: