4.9 sec in total
535 ms
4.1 sec
221 ms
Welcome to nenju.jp homepage info - get ready to check Nenju best content right away, or after learning these important things about nenju.jp
数珠・念珠・ラピスラズリ・翡翠などの天然石の通販を行っている翔龍念珠堂のホームページです。数珠の値段に自信があります。
Visit nenju.jpWe analyzed Nenju.jp page load time and found that the first response time was 535 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nenju.jp performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value5.6 s
18/100
25%
Value6.5 s
39/100
10%
Value200 ms
90/100
30%
Value0
100/100
15%
Value6.8 s
55/100
10%
535 ms
524 ms
669 ms
165 ms
330 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Nenju.jp, 92% (61 requests) were made to Nenju108.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Nenju108.jp.
Page size can be reduced by 22.4 kB (3%)
860.0 kB
837.6 kB
In fact, the total size of Nenju.jp main page is 860.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 823.6 kB which makes up the majority of the site volume.
Potential reduce by 12.2 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 2.7 kB, which is 17% 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 12.2 kB or 79% of the original size.
Potential reduce by 10.1 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. Nenju images are well optimized though.
Potential reduce by 50 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 7 (11%)
63
56
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nenju. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
nenju.jp
535 ms
nenju108.jp
524 ms
nenju108.jp
669 ms
stylesheet.css
165 ms
smooth.js
330 ms
jquery.min.js
660 ms
jquery.cookie.js
508 ms
jquery.sidr.min.js
509 ms
share.js
508 ms
analyticstracking.js
510 ms
style_pc.css
357 ms
style_sp.css
514 ms
analytics.js
37 ms
bg_body.gif
167 ms
bg_wrap.jpg
172 ms
bg_head.png
845 ms
logo.gif
176 ms
menu.png
171 ms
bg_container.png
172 ms
bg_navi.gif
330 ms
head-nav_home.gif
340 ms
head-nav_guide.gif
340 ms
head-nav_about.gif
341 ms
head-nav_order.gif
349 ms
head-nav_faq.gif
494 ms
head-nav_contact.gif
509 ms
blog.gif
510 ms
rakuten.gif
512 ms
facebook.gif
522 ms
pixel_trans.gif
657 ms
main-category_ttl.gif
677 ms
main-category_dansei.jpg
678 ms
main-category_josei.jpg
681 ms
main-category_shuha.jpg
696 ms
main-category_udewa.jpg
821 ms
main-category_bracelet.jpg
847 ms
main-category_fukusa.jpg
847 ms
main-category_parts.jpg
851 ms
main-category_set.jpg
869 ms
itoigawa_hisui.jpg
985 ms
silver.jpg
1014 ms
topbigsize.jpg
1184 ms
top16.jpg
1185 ms
tedukuri.jpg
1359 ms
main-banner_shijin.jpg
1042 ms
main-banner_bonji.jpg
1149 ms
main-banner_kouboku.jpg
1183 ms
main-banner_parts.jpg
1217 ms
main-banner_rutile.jpg
1290 ms
collect
12 ms
collect
28 ms
js
68 ms
main-banner_hisui.jpg
1191 ms
shop-subttl_kodawari.gif
1186 ms
shop-photo_naikan.jpg
1187 ms
main-shop_ttl.gif
1223 ms
main-shop_photo.jpg
1307 ms
bg_foot.gif
1197 ms
pc.png
1188 ms
sp.png
1188 ms
foot-nav_home.gif
1192 ms
foot-nav_guide.gif
1220 ms
foot-nav_about.gif
1153 ms
foot-nav_order.gif
1186 ms
foot-nav_faq.gif
1186 ms
foot-nav_contact.gif
1186 ms
nenju.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
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.
nenju.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
nenju.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
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nenju.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 Nenju.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
nenju.jp
Open Graph description is not detected on the main page of Nenju. 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: