6.5 sec in total
1 sec
5 sec
462 ms
Visit welox.jp now to see the best up-to-date Welox content for Japan and also check out these interesting facts you probably never knew about welox.jp
ホスティング、ホームページ制作、検索、ニュース、レンタルサーバなどを提供。
Visit welox.jpWe analyzed Welox.jp page load time and found that the first response time was 1 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
welox.jp performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value5.6 s
18/100
25%
Value7.0 s
32/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.8 s
97/100
10%
1023 ms
351 ms
353 ms
377 ms
388 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 40% of them (35 requests) were addressed to the original Welox.jp, 23% (20 requests) were made to Maps.googleapis.com and 22% (19 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Welox.jp.
Page size can be reduced by 509.0 kB (33%)
1.5 MB
1.0 MB
In fact, the total size of Welox.jp main page is 1.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. 55% of websites need less resources to load. Images take 808.0 kB which makes up the majority of the site volume.
Potential reduce by 13.5 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 13.5 kB or 72% of the original size.
Potential reduce by 10.3 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. Welox images are well optimized though.
Potential reduce by 473.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 473.9 kB or 70% of the original size.
Potential reduce by 11.2 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. Welox.jp needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 81% of the original size.
Number of requests can be reduced by 31 (38%)
81
50
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Welox. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
welox.jp
1023 ms
nc4.css
351 ms
import.css
353 ms
preimage.js
377 ms
smooth.pack.js
388 ms
screen01.css
339 ms
lightbox.css
389 ms
embed
140 ms
maps
58 ms
bg.jpg
335 ms
head_bg.gif
370 ms
main.jpg
1368 ms
navi01.jpg
387 ms
navi02.jpg
416 ms
navi03.jpg
433 ms
navi04.jpg
710 ms
navi05.jpg
749 ms
navi06.jpg
750 ms
spacer.gif
787 ms
content_bg.gif
787 ms
news_tit.gif
1076 ms
pagetop.jpg
1122 ms
service_tit.gif
1115 ms
recruit_tit.gif
1142 ms
access_tit.gif
1163 ms
about_tit.gif
1403 ms
embed
622 ms
js
44 ms
init_embed.js
29 ms
common.js
45 ms
map.js
57 ms
google4.png
63 ms
overlay.js
24 ms
util.js
60 ms
onion.js
60 ms
search_impl.js
61 ms
StaticMapService.GetMapImage
188 ms
stats.js
26 ms
ViewportInfoService.GetViewportInfo
81 ms
ViewportInfoService.GetViewportInfo
29 ms
transparent.png
25 ms
kh
45 ms
controls.js
12 ms
ViewportInfoService.GetViewportInfo
29 ms
css
77 ms
entity11.png
25 ms
mapcnt6.png
26 ms
tmapctrl.png
24 ms
vt
125 ms
vt
94 ms
vt
105 ms
vt
109 ms
vt
108 ms
vt
154 ms
vt
159 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
24 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
35 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
44 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
43 ms
AuthenticationService.Authenticate
13 ms
js
17 ms
StaticMapService.GetMapImage
520 ms
ViewportInfoService.GetViewportInfo
96 ms
ViewportInfoService.GetViewportInfo
18 ms
kh
36 ms
ViewportInfoService.GetViewportInfo
19 ms
vt
163 ms
vt
208 ms
vt
147 ms
vt
149 ms
vt
142 ms
vt
133 ms
vt
232 ms
vt
248 ms
vt
283 ms
vt
243 ms
AuthenticationService.Authenticate
15 ms
pagetop_on.jpg
550 ms
navi01.jpg
565 ms
navi02.jpg
558 ms
navi03.jpg
574 ms
navi04.jpg
576 ms
navi05.jpg
598 ms
navi06.jpg
917 ms
bg.jpg
907 ms
head_bg.jpg
1169 ms
priv_btn.jpg
998 ms
main.jpg
2179 ms
welox.jp accessibility score
welox.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
welox.jp SEO score
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Welox.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 Welox.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.
welox.jp
Open Graph description is not detected on the main page of Welox. 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: