8.2 sec in total
1.3 sec
6.7 sec
148 ms
Welcome to mosel.jp homepage info - get ready to check MOSEL best content for Japan right away, or after learning these important things about mosel.jp
モーゼル(MOSEL )とはドイツ、オーバーステンフェルトのスーパーチューナーブランドです。スタイリングデザイナーにイタリアのカーデザイナー、エルコーレ・スパーダを迎え、斬新な切り口で次世代のチューナーを目指しています。
Visit mosel.jpWe analyzed Mosel.jp page load time and found that the first response time was 1.3 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mosel.jp performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value7.5 s
4/100
25%
Value11.0 s
6/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value4.8 s
79/100
10%
1318 ms
675 ms
350 ms
365 ms
25 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 93% of them (42 requests) were addressed to the original Mosel.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Mosel.jp.
Page size can be reduced by 288.6 kB (10%)
3.0 MB
2.7 MB
In fact, the total size of Mosel.jp main page is 3.0 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. 25% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 18.6 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 18.6 kB or 74% of the original size.
Potential reduce by 51.7 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. MOSEL images are well optimized though.
Potential reduce by 183.6 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 183.6 kB or 69% of the original size.
Potential reduce by 34.8 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. Mosel.jp needs all CSS files to be minified and compressed as it can save up to 34.8 kB or 81% of the original size.
Number of requests can be reduced by 16 (36%)
44
28
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MOSEL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
mosel.jp
1318 ms
wp-emoji-release.min.js
675 ms
styles.css
350 ms
pagenavi-css.css
365 ms
css
25 ms
style.css
935 ms
lightbox.min.css
354 ms
jquery.js
1334 ms
jquery-migrate.min.js
550 ms
flexslider.css
382 ms
public.css
338 ms
jquery.form.min.js
820 ms
scripts.js
857 ms
comment-reply.min.js
539 ms
navigation.js
572 ms
jquery.touchwipe.min.js
719 ms
jquery.lightbox.min.js
992 ms
jquery.flexslider-min.js
1133 ms
analytics.js
15 ms
head.gif
192 ms
a18228d59d3143d4d1584853a98af695.jpg
1181 ms
efe01ae486e3cbdaf4c8f59ba2b709a9.jpg
1260 ms
IMGP9101.jpg
1497 ms
7d3f6b9e8b588e10efeadeff737ea657.jpg
1216 ms
975106bf9d98a0f351353479827310f4.jpg
1147 ms
c4e109a53a3cf7c37af55b4843e954dd.jpg
763 ms
7d3f6b9e8b588e10efeadeff737ea6571.jpg
1337 ms
975106bf9d98a0f351353479827310f41.jpg
2673 ms
c4e109a53a3cf7c37af55b4843e954dd-2.jpg
2529 ms
IMGP9454-1-2-1.jpg
2082 ms
IMGP9466-4.jpg
1800 ms
IMGP9469-31.jpg
2861 ms
ecf82913247ff81cc0b369a79d58e643.jpg
2902 ms
8a1ddecde8680294f7555992ccc9fbdc.jpg
3059 ms
04.jpg
3124 ms
IMGP1628-2.jpg
3709 ms
IMGP1650-2.jpg
4198 ms
IMGP1657-2.jpg
4253 ms
IMG_20160224_1725101-125x94.jpg
3079 ms
T1-125x83.jpg
3612 ms
IMGP9069-125x83.jpg
3255 ms
IMGP939211-125x77.jpg
3298 ms
IMGP1642-125x83.jpg
3432 ms
footer.gif
3471 ms
collect
19 ms
mosel.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.
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
Links do not have a discernible name
mosel.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
mosel.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mosel.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 Mosel.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.
mosel.jp
Open Graph description is not detected on the main page of MOSEL. 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: