4.2 sec in total
390 ms
3.6 sec
150 ms
Welcome to mini.jp homepage info - get ready to check MINI best content for Japan right away, or after learning these important things about mini.jp
MINI Japan 公式ウェブサイトへようこそ。MINIのモデルラインアップをはじめ、最新情報、MINI認定中古車情報、MINIオーナー向け情報などをお届けいたします。あなただけのMINI LIFEをはじめませんか。
Visit mini.jpWe analyzed Mini.jp page load time and found that the first response time was 390 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mini.jp performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value11.1 s
0/100
25%
Value14.5 s
1/100
10%
Value3,790 ms
1/100
30%
Value0.131
81/100
15%
Value30.3 s
0/100
10%
390 ms
646 ms
58 ms
309 ms
288 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 62% of them (68 requests) were addressed to the original Mini.jp, 6% (7 requests) were made to Pixel.mathtag.com and 6% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Mini.jp.
Page size can be reduced by 278.7 kB (18%)
1.6 MB
1.3 MB
In fact, the total size of Mini.jp main page is 1.6 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 140.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 140.1 kB or 85% of the original size.
Potential reduce by 32.5 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. MINI images are well optimized though.
Potential reduce by 106.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 106.0 kB or 50% of the original size.
Number of requests can be reduced by 47 (46%)
102
55
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MINI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
mini.jp
390 ms
www.mini.jp
646 ms
generic.js
58 ms
generic.css
309 ms
m_new_main_stage.css
288 ms
m_new_new_main_stage.js
362 ms
is_script.js
263 ms
smartphone.js
154 ms
s_retargeting.js
568 ms
conversion.js
62 ms
bmw201506
943 ms
901 ms
mini_print.gif
269 ms
logo_be_mini.png
75 ms
bodytype_new_mini_5door.png
151 ms
bodytype_new_mini.png
89 ms
bodytype_new_mini_f54.png
139 ms
bodytype_new_mini_f57.png
93 ms
bodytype_mini_countryman.png
96 ms
bodytype_mini_paceman.png
113 ms
bodytype_jcw.png
114 ms
bodytype_mini_ray.png
114 ms
find_my_mini.png
152 ms
find_my_mini_hover.jpg
370 ms
compare_my_mini.jpg
283 ms
compare_my_mini_hover.jpg
507 ms
icon_search.png
159 ms
model_navigation_big.png
166 ms
20160205_f57_small_img.jpg
291 ms
20160216_mop_small_img.gif
448 ms
japan.jpg
498 ms
facebook.gif
452 ms
pixel_grey.png
299 ms
mini_hatch_noflash_black.PNG
296 ms
mini_convertible_noflash_black.png
316 ms
mini_clubman_noflash_black.PNG
326 ms
mini_clubvan_noflash_black.png
327 ms
mini_crossover_noflash_black.png
332 ms
mini_paceman_noflash_black.png
333 ms
mini_jcw_noflash_black.PNG
339 ms
mini_yours_noflash_black_en.png
337 ms
spr_content.png
299 ms
index.html
321 ms
car_side.png
179 ms
wtid.js
5 ms
0b266876bcbc0758_1915.js
386 ms
dcs.gif
6 ms
style.css
199 ms
f54-top-teaser_LSM.jpg
1452 ms
114 ms
pix
375 ms
all.js
305 ms
print.css
41 ms
jsapi
51 ms
profile
348 ms
mini_5door_quickfacts.html
139 ms
icon_share.png
16 ms
facebook.gif
149 ms
myspace.gif
212 ms
twitter.gif
148 ms
favourites.gif
170 ms
icon_sound_on.png
145 ms
icon_print.png
148 ms
dummy_facebook.png
168 ms
dummy_twitter.png
168 ms
dummy_gplus.png
156 ms
index.html
300 ms
index.html
288 ms
22 ms
61 ms
default+en.css
6 ms
default+en.I.js
17 ms
js
29 ms
async-ads.js
63 ms
google_custom_search_watermark.gif
26 ms
i.js
56 ms
small-logo.png
20 ms
model_new_mini_5door_default.png
37 ms
link_arrow_standard_active.png
33 ms
style.css
126 ms
autumn-winter_campaign_880x370_2.jpg
1179 ms
122 ms
style.css
163 ms
980.jpg
771 ms
xd_arbiter.php
223 ms
xd_arbiter.php
433 ms
combo
164 ms
js
36 ms
img
26 ms
iframe
33 ms
pb.html
11 ms
img
80 ms
pix
154 ms
pixel
23 ms
325 ms
img
43 ms
655 ms
331 ms
pixel
19 ms
163 ms
print.css
8 ms
rep
160 ms
pixel
57 ms
img
57 ms
link_arrow_standard_inactive.png
42 ms
links_background.png
10 ms
body_type_bg.jpg
178 ms
floor.jpg
135 ms
chevron_black.png
12 ms
mini.jp 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
Buttons do not have an accessible name
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
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.
mini.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
mini.jp SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mini.jp can be misinterpreted by Google and other search engines. Our service has detected that English 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 Mini.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.
mini.jp
Open Graph description is not detected on the main page of MINI. 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: