4.7 sec in total
931 ms
3.5 sec
184 ms
Welcome to baseu.jp homepage info - get ready to check BASE U best content for Japan right away, or after learning these important things about baseu.jp
ショップの開設から日々の運用、導入事例まで、BASEでネットショップを運営するときに知りたい、あらゆる情報が載っています。BASEのことは、「BASE U」に。
Visit baseu.jpWe analyzed Baseu.jp page load time and found that the first response time was 931 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
baseu.jp performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value10.7 s
0/100
25%
Value5.1 s
62/100
10%
Value140 ms
95/100
30%
Value0
100/100
15%
Value12.2 s
15/100
10%
931 ms
33 ms
387 ms
24 ms
584 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 16% of them (16 requests) were addressed to the original Baseu.jp, 24% (24 requests) were made to Static.xx.fbcdn.net and 9% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (970 ms) belongs to the original domain Baseu.jp.
Page size can be reduced by 195.2 kB (56%)
350.7 kB
155.5 kB
In fact, the total size of Baseu.jp main page is 350.7 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. Javascripts take 182.1 kB which makes up the majority of the site volume.
Potential reduce by 33.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 33.5 kB or 75% of the original size.
Potential reduce by 6.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. BASE U images are well optimized though.
Potential reduce by 113.5 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 113.5 kB or 62% of the original size.
Potential reduce by 41.9 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. Baseu.jp needs all CSS files to be minified and compressed as it can save up to 41.9 kB or 81% of the original size.
Number of requests can be reduced by 60 (65%)
93
33
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BASE U. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
baseu.jp
931 ms
slim-081711.css
33 ms
pagenavi-css.css
387 ms
css
24 ms
style.css
584 ms
wpp.css
385 ms
wp-emoji-release.min.js
532 ms
topLogo.png
357 ms
navPulldownBtn.png
292 ms
button-only.gif
310 ms
bookmark_button.js
357 ms
navigation.js
320 ms
wp-embed.min.js
322 ms
jquery-1.9.1.min.js
970 ms
main.js
419 ms
187 ms
widgets.js
45 ms
head_bg.png
210 ms
navMenuHover.png
198 ms
logoForOpening.png
196 ms
logoForManagement.png
227 ms
logoForPreparation.png
196 ms
ga.js
31 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
48 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
53 ms
__utm.gif
38 ms
reset.css
4 ms
entry-button.css
4 ms
bbtn-s_v3.png
4 ms
sdk.js
235 ms
btn.js
122 ms
plusone.js
182 ms
segmentation.js
145 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
33 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
50 ms
syndication
114 ms
344682337541439489
312 ms
cnt
343 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
24 ms
cb=gapi.loaded_0
23 ms
147 ms
xd_arbiter.php
140 ms
xd_arbiter.php
272 ms
1f431.png
23 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
4 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
8 ms
Y9k6QM5o_normal.png
134 ms
6xhAOt9v_normal.jpg
130 ms
CcY6d86UUAAAu9v.jpg:small
131 ms
beacon.html
126 ms
pixel
50 ms
cs
334 ms
Pug
43 ms
set
303 ms
sd
6 ms
sync
6 ms
tap.php
7 ms
like.php
84 ms
pixel
36 ms
sync
316 ms
like_box.php
196 ms
rU2ubZ6l1Q5.js
285 ms
LVx-xkvaJ0b.png
235 ms
siylcCr24Vv.css
121 ms
0q9EiyOzKa_.css
123 ms
k9pcUClPi_g.css
130 ms
_rx8naC75Dy.js
207 ms
x5F9OMjKyLw.js
229 ms
ICDbTSzjQEg.js
156 ms
TTCre3391I0.js
163 ms
rFmE1g6Dkoz.js
288 ms
7cm7D75Y0Sf.js
241 ms
C-h3nYPqETO.js
199 ms
oRoBXlHCpEy.js
199 ms
336JejShbZp.js
241 ms
sj-JwAJi4AH.js
272 ms
DKRU1bYTkTw.js
246 ms
ZNPAadQNc33.js
266 ms
W0OV23mIOyO.js
268 ms
36TdwhIHusi.js
274 ms
mapuser
148 ms
jot.html
3 ms
sync
348 ms
sync
314 ms
11890982_970581896297037_1380853877102004925_n.jpg
176 ms
58872_527877923900772_1861724509_n.png
215 ms
11222403_530073153816016_9196004890480817300_n.jpg
255 ms
383485_130825427050302_1949643665_n.jpg
285 ms
11988646_882958821782001_6259531523627528225_n.jpg
285 ms
575673_320228774728228_1896250007_n.jpg
286 ms
1375871_983599648324685_5441947917278295156_n.jpg
292 ms
10420760_10152262811741700_1577411982971361057_n.jpg
293 ms
12096576_10156071811860394_5015539816610520749_n.jpg
295 ms
wL6VQj7Ab77.png
74 ms
s7jcwEQH7Sx.png
74 ms
pUFVdPjIRct.png
40 ms
I6-MnjEovm5.js
40 ms
vlXaquuXMrr.js
76 ms
baseu.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
[id] attributes on active, focusable elements are not unique
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
<object> elements do not have alternate text
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
baseu.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
baseu.jp 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
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 doesn't use legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Baseu.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 Baseu.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.
baseu.jp
Open Graph data is detected on the main page of BASE U. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: