5.8 sec in total
349 ms
4.8 sec
700 ms
Click here to check amazing Nepia content for Japan. Otherwise, check out these important facts you probably never knew about nepia.co.jp
人や暮らしだけでなく、私たちが生きる地球も見つめて。ふだんの暮らしに寄り添い、すべての毎日を支え続ける。【森のnepia】王子ネピアのオフィシャルサイトです。
Visit nepia.co.jpWe analyzed Nepia.co.jp page load time and found that the first response time was 349 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
nepia.co.jp performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value21.6 s
0/100
25%
Value9.0 s
15/100
10%
Value610 ms
48/100
30%
Value0.207
60/100
15%
Value18.2 s
3/100
10%
349 ms
693 ms
50 ms
346 ms
59 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 81% of them (48 requests) were addressed to the original Nepia.co.jp, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Nepia.co.jp.
Page size can be reduced by 33.2 kB (3%)
1.2 MB
1.2 MB
In fact, the total size of Nepia.co.jp main page is 1.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 22.0 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 7.8 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 22.0 kB or 84% of the original size.
Potential reduce by 11.2 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. Nepia images are well optimized though.
Number of requests can be reduced by 10 (18%)
57
47
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nepia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
nepia.co.jp
349 ms
www.nepia.co.jp
693 ms
slick.css
50 ms
top.css
346 ms
vegas.min.css
59 ms
jquery-3.7.1.js
43 ms
slick.min.js
61 ms
vegas.min.js
71 ms
slick-slide.js
515 ms
kv-slide.js
517 ms
main.js
525 ms
css2
41 ms
notosansjp.css
65 ms
gtm.js
163 ms
top.svg
177 ms
sprite.svg
264 ms
logo.svg
267 ms
%E3%80%90%E3%82%AD%E3%83%BC%E3%83%93%E3%82%B8%E3%83%A5%E3%82%A2%E3%83%AB%E3%83%90%E3%83%8A%E3%83%BC%E3%80%91800x500_0409.jpg
1095 ms
%E3%80%90%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B3%E3%83%90%E3%83%8A%E3%83%BC%E3%80%91800x500_0409.jpg
1506 ms
bottom.svg
431 ms
toppage-catch.webp
434 ms
bg-mid-sec.webp
3330 ms
value-img01.webp
1337 ms
value-bg01.webp
765 ms
value-bg02.png
601 ms
value-img02.webp
1101 ms
product-bg.webp
932 ms
prodact01.webp
1432 ms
prodact02.webp
1270 ms
prodact07.webp
1271 ms
prodact03.webp
1445 ms
prodact04.webp
1440 ms
prodact22.webp
1510 ms
prodact05.webp
1764 ms
prodact21.webp
1611 ms
home-mask01.png
1620 ms
prodact10.webp
1672 ms
prodact08.webp
1678 ms
prodact09.webp
1780 ms
prodact20.webp
1792 ms
prodact11.webp
2003 ms
prodact12.webp
1849 ms
prodact13.webp
1932 ms
prodact14.webp
1949 ms
prodact15.webp
1964 ms
prodact16.webp
2017 ms
prodact17.webp
2108 ms
font
55 ms
font
60 ms
font
83 ms
prodact18.webp
2032 ms
pdf-icon.svg
2042 ms
bn-top01.webp
2075 ms
icon-line.svg
2016 ms
icon-x.svg
2019 ms
dot.png
2023 ms
top_kv_01.webp
2047 ms
top_kv_02.webp
2412 ms
top_kv_03.webp
2091 ms
nepia.co.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
nepia.co.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
Page has valid source maps
nepia.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nepia.co.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 Nepia.co.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.
nepia.co.jp
Open Graph data is detected on the main page of Nepia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: