11.7 sec in total
791 ms
10.4 sec
476 ms
Visit vortis.jp now to see the best up-to-date Vortis content for Japan and also check out these interesting facts you probably never knew about vortis.jp
パワー・スピード・結束力を兼ね備え、観客を興奮の渦に巻き込むような戦いを見せることを目指しています。
Visit vortis.jpWe analyzed Vortis.jp page load time and found that the first response time was 791 ms and then it took 10.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.
vortis.jp performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value23.5 s
0/100
25%
Value40.0 s
0/100
10%
Value44,290 ms
0/100
30%
Value2.007
0/100
15%
Value86.2 s
0/100
10%
791 ms
338 ms
1181 ms
739 ms
339 ms
Our browser made a total of 294 requests to load all elements on the main page. We found that 79% of them (231 requests) were addressed to the original Vortis.jp, 4% (11 requests) were made to Google.com and 2% (7 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Vortis.jp.
Page size can be reduced by 1.4 MB (29%)
4.7 MB
3.3 MB
In fact, the total size of Vortis.jp main page is 4.7 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. 80% 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.2 MB which makes up the majority of the site volume.
Potential reduce by 68.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 68.7 kB or 77% of the original size.
Potential reduce by 344.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. Obviously, Vortis needs image optimization as it can save up to 344.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 703.1 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 703.1 kB or 65% of the original size.
Potential reduce by 257.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. Vortis.jp needs all CSS files to be minified and compressed as it can save up to 257.7 kB or 82% of the original size.
Number of requests can be reduced by 55 (19%)
286
231
The browser has sent 286 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vortis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
vortis.jp
791 ms
css_browser_selector.js
338 ms
jquery-1.9.1.js
1181 ms
megamenu-set.js
739 ms
function.js
339 ms
import.css
360 ms
index.css
371 ms
jquery.easing.js
503 ms
lofslider.js
673 ms
lofslider.css
538 ms
element.js
48 ms
348 ms
reset.css
177 ms
common.css
336 ms
megamenu.css
171 ms
search.css
181 ms
vortis-logo.png
376 ms
vortis-slogan2016.png
505 ms
glnavi-01.gif
229 ms
glnavi-02.gif
233 ms
glnavi-03.gif
229 ms
glnavi-04.gif
234 ms
glnavi-05.gif
374 ms
glnavi-06.gif
375 ms
glnavi-07.gif
406 ms
glnavi-08.gif
407 ms
glnavi-09.gif
540 ms
bnr-mypagelogin.png
802 ms
btn-line.gif
558 ms
ttl-result.gif
612 ms
top508_img.gif
810 ms
ttl-nextgame.gif
801 ms
ttl-otherinfo.gif
802 ms
ttl-ranking.gif
803 ms
ttl-attendance-j2.gif
809 ms
bnr-tsv.gif
909 ms
bnr-tokushimaguide.jpg
1025 ms
btn_ticket.gif
912 ms
bnr-clubtoto.gif
940 ms
skyperfectv-1602.gif
1339 ms
top_thumbnail.php
2963 ms
top_thumbnail.php
2408 ms
top_thumbnail.php
2101 ms
top_thumbnail.php
2236 ms
top_thumbnail.php
2758 ms
top_thumbnail.php
2862 ms
top_thumbnail.php
2291 ms
top_thumbnail.php
2433 ms
top_thumbnail.php
2478 ms
top_thumbnail.php
2597 ms
top_thumbnail.php
2632 ms
header.js
328 ms
top_thumbnail.php
2664 ms
cse.js
133 ms
translateelement.css
63 ms
main.js
132 ms
widgets.js
144 ms
PJgDEjdGl7w
256 ms
analytics.js
82 ms
jsapi
651 ms
element_main.js
82 ms
all.js
194 ms
176 ms
155 ms
sponsor.html
2559 ms
hsmPbUGHOLs
176 ms
news.php
2622 ms
school.php
2636 ms
topics.php
2750 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
188 ms
collect
61 ms
translate_24dp.png
109 ms
l
73 ms
cleardot.gif
65 ms
93 ms
75 ms
tokushima.html
162 ms
btn-thums.png
2572 ms
bnr-t-guide.jpg
2653 ms
bnr-manner-s.jpg
2675 ms
69 ms
te_ctrl3.gif
33 ms
googlelogo_color_68x28dp.png
22 ms
loading.gif
47 ms
www-embed-player-vflZsBgOl.css
112 ms
www-embed-player.js
182 ms
base.js
254 ms
30 ms
bnr-kojinpoint2016.jpg
2797 ms
bnr-goods2016.jpg
3041 ms
xd_arbiter.php
158 ms
xd_arbiter.php
400 ms
te_bk.gif
17 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
67 ms
reset.css
292 ms
jheader.css
331 ms
bnr-blog.jpg
2641 ms
blog_thumbnail.php
2603 ms
blog_thumbnail.php
2645 ms
bnr-guide.jpg
2805 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
41 ms
ad_status.js
55 ms
jot
309 ms
bnr-ticket.jpg
2524 ms
bnr-gallery4.jpg
2524 ms
bnr-voice2.jpg
2733 ms
bnr-school.jpg
2583 ms
bnr-melmaga.jpg
2696 ms
bnr-onlineshop.jpg
2684 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
130 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
205 ms
default+ja.css
14 ms
minimalist.css
29 ms
default+ja.I.js
28 ms
gpt.js
80 ms
jheader_jlogo.png
194 ms
jheader_team_emb_s_bw.png
503 ms
linkid.js
75 ms
minimalist.css
233 ms
bnr-vorsta.jpg
2654 ms
pubads_impl_81.js
98 ms
bnr-facebook.gif
2664 ms
bnr-line.gif
2676 ms
async-ads.js
144 ms
google_custom_search_watermark.gif
61 ms
small-logo.png
61 ms
clear.gif
62 ms
collect
119 ms
bnr-linestamp.jpg
2637 ms
ads
71 ms
container.html
54 ms
17975101117481847783
16 ms
10310348945490554035
19 ms
osd.js
6 ms
bnr-twitter.gif
2345 ms
activeview
14 ms
activeview
14 ms
btn-highlight.gif
1602 ms
logo-skyper.gif
1500 ms
bnr-vortischannel.gif
1494 ms
bnr-tomidaiseat.jpg
1379 ms
bnr_academy.gif
1396 ms
bnr-supportstaff.gif
1385 ms
bnr-cheerleader.gif
1274 ms
bnr-chushikoku.jpg
1279 ms
bnr-clasico.jpg
1304 ms
bnr-jihanki.gif
1198 ms
sponsor.css
1215 ms
news.css
1238 ms
jquery.carouFredSel-6.2.1.js
1181 ms
snews_icon_4.gif
551 ms
bnr-infovorta.gif
1252 ms
bnr-respect.jpg
1180 ms
gotop.gif
1184 ms
img-vortismascot.gif
1184 ms
back-head-ind3.gif
1187 ms
img-index.jpg
1357 ms
back-tnavi.gif
1122 ms
glnavi-01on.gif
1136 ms
glnavi-02on.gif
1142 ms
back-mega.png
1124 ms
arrow-gr02.png
1056 ms
glnavi-03on.gif
1116 ms
glnavi-04on.gif
1076 ms
glnavi-05on.gif
1086 ms
glnavi-06on.gif
1079 ms
glnavi-07on.gif
1055 ms
glnavi-08on.gif
1082 ms
glnavi-09on.gif
1080 ms
back-black.gif
1068 ms
arrow-wh01.png
1068 ms
arrow-wh02.png
1094 ms
back-gray.gif
1054 ms
arrow-red.png
1068 ms
line-05.gif
1088 ms
loader.png
1060 ms
slide-prev.png
1058 ms
back-thum.png
1108 ms
slide-next.png
1054 ms
back-blue.gif
1081 ms
h3-index.gif
1094 ms
line-01.gif
1053 ms
rss01.png
1057 ms
arrow-gr01.png
1080 ms
blog-ttl.gif
1081 ms
blog-arrow.png
1040 ms
blog-rss.png
1025 ms
arrow-blue.png
1017 ms
back-fnavi01.gif
1057 ms
back-fnavi02.gif
1065 ms
line-03.gif
1098 ms
back-foot.gif
1094 ms
news_ico_media.gif
1039 ms
news_ico_news.gif
1023 ms
slide-thon.png
1014 ms
bnr-c01.gif
1049 ms
bnr-c02.gif
1070 ms
bnr-c03.gif
1066 ms
bnr-c04.gif
1045 ms
bnr-c05.gif
1030 ms
bnr-c06.gif
1014 ms
bnr-c07.gif
1031 ms
bnr-c08.gif
1085 ms
bnr-c09.gif
1054 ms
bnr-c10.gif
1051 ms
bnr-d01.gif
1036 ms
bnr-d02.gif
1014 ms
bnr-d03.gif
1015 ms
bnr-d04.gif
1102 ms
bnr-d05.gif
1041 ms
bnr-d88.gif
1056 ms
bnr-d06.gif
1045 ms
bnr-d07.gif
1010 ms
bnr-d08.gif
1012 ms
bnr-d09.gif
1080 ms
bnr-d10.gif
1057 ms
bnr-d11.gif
1052 ms
bnr-d12.gif
1059 ms
bnr-d13.gif
1009 ms
bnr-d14.gif
1010 ms
bnr-d15.gif
1065 ms
bnr-d16.gif
1061 ms
bnr-d17.gif
1059 ms
bnr-d18.gif
1050 ms
bnr-d19.gif
1025 ms
bnr-d20.gif
1009 ms
bnr-d82.gif
1048 ms
bnr-d21.gif
1069 ms
bnr-d22.gif
1053 ms
bnr-d23.gif
1054 ms
bnr-d24.gif
1039 ms
bnr-d25.gif
1010 ms
bnr-d89.gif
1030 ms
bnr-d26.gif
1055 ms
bnr-d27.gif
1059 ms
bnr-d28.gif
1065 ms
bnr-d29.gif
1050 ms
bnr-d30.gif
1010 ms
bnr-d31.gif
1015 ms
bnr-d32.gif
1056 ms
bnr-d33.gif
1054 ms
bnr-d34.gif
1075 ms
bnr-d35.gif
1049 ms
bnr-d36.gif
1020 ms
bnr-d37.gif
1010 ms
bnr-d38.gif
1045 ms
bnr-d39.gif
1054 ms
bnr-d86.gif
1056 ms
bnr-d44.gif
1072 ms
bnr-d40.gif
1032 ms
bnr-d41.gif
1011 ms
bnr-d42.gif
1029 ms
bnr-d43.gif
1054 ms
bnr-d45.gif
1050 ms
bnr-d46.gif
1086 ms
bnr-d47.gif
1048 ms
bnr-d48.gif
1014 ms
bnr-d49.gif
1013 ms
bnr-d50.gif
1049 ms
bnr-d85.gif
1054 ms
bnr-d51.gif
1081 ms
bnr-d84.gif
1066 ms
bnr-d83.gif
1011 ms
bnr-d52.gif
1010 ms
bnr-d53.gif
1038 ms
bnr-d54.gif
1051 ms
bnr-d55.gif
1081 ms
bnr-d56.gif
1081 ms
bnr-d57.gif
1012 ms
bnr-d58.gif
1010 ms
bnr-d59.gif
1031 ms
bnr-d60.gif
1041 ms
bnr-d61.gif
1081 ms
bnr-d62.gif
1098 ms
bnr-d63.gif
1012 ms
bnr-d64.gif
1009 ms
bnr-d65.gif
1024 ms
bnr-d87.gif
1054 ms
bnr-d66.gif
1086 ms
bnr-d67.gif
1082 ms
bnr-d68.gif
1034 ms
bnr-d69.gif
1010 ms
bnr-d70.gif
1016 ms
bnr-d71.gif
1062 ms
bnr-d72.gif
1081 ms
bnr-d73.gif
1071 ms
bnr-d74.gif
1048 ms
bnr-d75.gif
1010 ms
bnr-d76.gif
1008 ms
bnr-d77.gif
1068 ms
bnr-d78.gif
1057 ms
bnr-d79.gif
1076 ms
bnr-d80.gif
1062 ms
bnr-d81.gif
1010 ms
vortis.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
vortis.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
Browser errors were logged to the console
Page has valid source maps
vortis.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vortis.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vortis.jp main page’s claimed encoding is shift_jis. 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.
vortis.jp
Open Graph description is not detected on the main page of Vortis. 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: