5.9 sec in total
633 ms
4.8 sec
443 ms
Welcome to nudymore.jp homepage info - get ready to check Nudymore best content for Japan right away, or after learning these important things about nudymore.jp
日本初の下地専門ブランド。その歴史は、メイクを変える「伝説の下地」から始まりました。
Visit nudymore.jpWe analyzed Nudymore.jp page load time and found that the first response time was 633 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
nudymore.jp performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value8.7 s
1/100
25%
Value5.3 s
58/100
10%
Value370 ms
71/100
30%
Value0.531
14/100
15%
Value8.9 s
35/100
10%
633 ms
703 ms
197 ms
373 ms
513 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 86% of them (50 requests) were addressed to the original Nudymore.jp, 5% (3 requests) were made to Googletagmanager.com and 3% (2 requests) were made to B97.yahoo.co.jp. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Nudymore.jp.
Page size can be reduced by 100.4 kB (5%)
1.9 MB
1.8 MB
In fact, the total size of Nudymore.jp main page is 1.9 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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 16.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 16.5 kB or 73% of the original size.
Potential reduce by 46.6 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. Nudymore images are well optimized though.
Potential reduce by 35.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 35.1 kB or 48% of the original size.
Potential reduce by 2.3 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. Nudymore.jp needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 11% of the original size.
Number of requests can be reduced by 10 (18%)
56
46
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nudymore. 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 as a result speed up the page load time.
nudymore.jp
633 ms
nudymore.jp
703 ms
style.min.css
197 ms
res.css
373 ms
meanmenu.css
513 ms
jquery-1.9.1.js
24 ms
jquery.meanmenu.js
527 ms
respond.min.js
528 ms
jQueryAutoHeight-0.04.js
529 ms
common.js
528 ms
bgi_top01.jpg
313 ms
gnavi000.png
172 ms
gnavi001.png
173 ms
gnavi002.png
175 ms
gnavi003.png
176 ms
gnavi004.png
176 ms
main_txt01.png
411 ms
sm_top01.jpg
412 ms
sm_top02.jpg
410 ms
s02_txt01.png
410 ms
sm_top03.jpg
576 ms
sm_top04.jpg
637 ms
sm_top05.jpg
642 ms
s03_txt01.png
606 ms
sm_top06.jpg
599 ms
sm_top07.jpg
645 ms
s04_txt01.png
780 ms
sm_top08.jpg
794 ms
sm_top09.jpg
833 ms
media02.png
1913 ms
sm_top10.jpg
1322 ms
f_ing.png
872 ms
sm_top11.jpg
1146 ms
sm_top12.jpg
966 ms
sm_top13.jpg
1009 ms
new.png
1048 ms
img_top10.png
1161 ms
companyName.png
1222 ms
tell.png
1263 ms
contact.png
1345 ms
copy.png
1383 ms
gtm.js
67 ms
bg_h.png
1372 ms
logo02.png
1421 ms
shop02.png
1478 ms
gnavi001_off.png
1496 ms
gnavi002_off.png
1536 ms
js
56 ms
destination
172 ms
116058.ct.js
171 ms
conversion.js
694 ms
gnavi003_off.png
1401 ms
gnavi004_off.png
1449 ms
bgi_top02.jpg
2565 ms
bgi_top03.jpg
1716 ms
bgi_top04.jpg
1826 ms
conversion_async.js
1523 ms
587 ms
nudymore.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
Links do not have a discernible name
nudymore.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
nudymore.jp SEO score
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nudymore.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 Nudymore.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.
nudymore.jp
Open Graph description is not detected on the main page of Nudymore. 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: