5.7 sec in total
555 ms
4.7 sec
462 ms
Click here to check amazing OMNIST content. Otherwise, check out these important facts you probably never knew about omnist.jp
3秒後、ぷるん!100%食べられる食材原料から作った"素肌においしい"スキンケアブランド「OMNIST -オムニスト-」。思わずそっと触れたくなるほどの、極上の素肌に。
Visit omnist.jpWe analyzed Omnist.jp page load time and found that the first response time was 555 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
omnist.jp performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value13.2 s
0/100
25%
Value14.6 s
1/100
10%
Value610 ms
49/100
30%
Value0.485
17/100
15%
Value13.6 s
11/100
10%
555 ms
1481 ms
491 ms
35 ms
658 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 81% of them (71 requests) were addressed to the original Omnist.jp, 6% (5 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Omnist.jp.
Page size can be reduced by 792.9 kB (29%)
2.7 MB
1.9 MB
In fact, the total size of Omnist.jp main page is 2.7 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. 60% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 70.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. This page needs HTML code to be minified as it can gain 25.5 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 70.5 kB or 84% of the original size.
Potential reduce by 5.9 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. OMNIST images are well optimized though.
Potential reduce by 348.2 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 348.2 kB or 58% of the original size.
Potential reduce by 368.4 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. Omnist.jp needs all CSS files to be minified and compressed as it can save up to 368.4 kB or 88% of the original size.
Number of requests can be reduced by 44 (55%)
80
36
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OMNIST. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
omnist.jp
555 ms
omnist.jp
1481 ms
wp-emoji-release.min.js
491 ms
font-awesome.min.css
35 ms
arconix-shortcodes.min.css
658 ms
styles.css
522 ms
swipebox.min.css
526 ms
wpsm-style.css
623 ms
bootstrap.css
1303 ms
prettyPhoto.css
815 ms
animate.css
1216 ms
style.css
1577 ms
wpp.css
784 ms
dynamic.css
821 ms
jquery.js
1268 ms
jquery-migrate.min.js
978 ms
jquery.swipebox.min.js
986 ms
front.js
1141 ms
modernizr.custom.js
1150 ms
css
37 ms
jquery.min.js
24 ms
slick.js
1641 ms
scripts.js
858 ms
wpsm-script.js
931 ms
bootstrap.min.js
971 ms
modernizr-ie.js
1006 ms
jquery.easing.1.3.min.js
1021 ms
waypoints.min.js
1104 ms
jquery.simple-text-rotator.min.js
1132 ms
jquery.nicescroll.min.js
1337 ms
slick.min.js
1269 ms
jquery.prettyPhoto.js
1291 ms
jquery.knob.min.js
1312 ms
jquery.fitvids.js
1312 ms
js
52 ms
scripts.js
1357 ms
wp-embed.min.js
1361 ms
css
17 ms
css
26 ms
sdk.js
97 ms
ga.js
94 ms
logo_pc.png
261 ms
cart_icon.png
264 ms
main_image_pc.jpg
628 ms
main_image_sp.jpg
465 ms
top_float_baner.png
311 ms
banner_trial.jpg
825 ms
banner_store.jpg
782 ms
cont-h2_bg.png
425 ms
press_img_01.jpg
473 ms
press_img_02.jpg
588 ms
press_img_03.jpg
628 ms
press_img_04.jpg
637 ms
press_img_05.jpg
750 ms
press_img_06.jpg
802 ms
14543f6603a53326885e605b98d1b110_m-163x115.jpg
791 ms
qa_next.png
800 ms
005-163x115.jpg
911 ms
98d84608511d02d408eeea51cbc490da_m-163x115.jpg
955 ms
a5a95c69ef901f30142d7ffbf8dd313e_m-163x115.jpg
954 ms
top_about_01.jpg
964 ms
top_about_02.jpg
977 ms
top_about_03.jpg
989 ms
cont-btn_01.jpg
1072 ms
lineup_img01.jpg
1116 ms
lineup_btn_bg.gif
1128 ms
lineup_img02.jpg
1126 ms
lineup_img03.jpg
1153 ms
cont-btn_02.jpg
1153 ms
voice_img01.jpg
1160 ms
voice_img02.jpg
1205 ms
fontawesome-webfont.woff
37 ms
NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzZQ.woff
38 ms
NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZQ.woff
38 ms
NaPecZTIAOhVxoMyOr9n_E7fdMPmCw.woff
59 ms
NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzZQ.woff
59 ms
NaPDcZTIAOhVxoMyOr9n_E7ffAzHGItzZQ.woff
60 ms
sdk.js
15 ms
__utm.gif
45 ms
voice_img03.jpg
1192 ms
101 ms
voice_img04.jpg
1185 ms
voice_img05.jpg
1210 ms
cont-btn_03.jpg
1159 ms
foot_sns_01.jpg
1232 ms
foot_sns_02.jpg
1277 ms
foot_sns_03.jpg
1196 ms
ajax-loader.gif
1216 ms
omnist.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
omnist.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
omnist.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 uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omnist.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Omnist.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.
omnist.jp
Open Graph data is detected on the main page of OMNIST. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: