4.4 sec in total
610 ms
3.5 sec
314 ms
Welcome to nocto.jp homepage info - get ready to check Nocto best content for Japan right away, or after learning these important things about nocto.jp
オールドレンズの専門店NOCTOです。ライカやM42マウントなどのオールドレンズならお任せください。
Visit nocto.jpWe analyzed Nocto.jp page load time and found that the first response time was 610 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
nocto.jp performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value7.9 s
3/100
25%
Value7.3 s
29/100
10%
Value120 ms
97/100
30%
Value0
100/100
15%
Value6.7 s
56/100
10%
610 ms
310 ms
330 ms
336 ms
317 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 32% of them (37 requests) were addressed to the original Nocto.jp, 25% (29 requests) were made to Static.xx.fbcdn.net and 23% (26 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Bricolage.sakura.ne.jp.
Page size can be reduced by 132.1 kB (23%)
575.0 kB
442.9 kB
In fact, the total size of Nocto.jp main page is 575.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. 70% of websites need less resources to load. Images take 447.6 kB which makes up the majority of the site volume.
Potential reduce by 41.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. 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 41.2 kB or 78% of the original size.
Potential reduce by 43.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. Nocto images are well optimized though.
Potential reduce by 3.3 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 3.3 kB or 15% of the original size.
Potential reduce by 44.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. Nocto.jp needs all CSS files to be minified and compressed as it can save up to 44.4 kB or 83% of the original size.
Number of requests can be reduced by 42 (37%)
113
71
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nocto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
nocto.jp
610 ms
m_sys_common.css
310 ms
import.css
330 ms
script.js
336 ms
check_history.css
317 ms
pager.css
331 ms
shopdetail.css
332 ms
ranking.css
336 ms
basket.css
333 ms
security.css
355 ms
category_menu.css
638 ms
topicpath.css
651 ms
catalog.css
664 ms
topimg.jpg
1713 ms
count2.makeshop.jp
520 ms
logo-bar.gif
529 ms
login_btn.gif
531 ms
search.gif
531 ms
kobutushow-ban.gif
1086 ms
mainte-ban.gif
1099 ms
modAngenieuxI_ban200.gif
1085 ms
modAngenieuxII_ban200.gif
1085 ms
Trioplan_ban200x80-1.jpg
1084 ms
SWITAR_H16RX_ban200x80.jpg
1204 ms
left_edge.gif
188 ms
right_edge.gif
183 ms
0000000010223.jpg
320 ms
0000000010183.jpg
320 ms
0020010000753.jpg
349 ms
iconW.gif
355 ms
0000000009673.jpg
492 ms
0020010001373.jpg
524 ms
0000000008633.jpg
635 ms
0000000008613.jpg
651 ms
0020010000153.jpg
657 ms
0020010000583.jpg
676 ms
0000000008753.jpg
1080 ms
0000000010203.jpg
1092 ms
0000000010093.jpg
1093 ms
0100030000503.jpg
1093 ms
0100030000103.jpg
1092 ms
0000000009023.jpg
1268 ms
iconQ.gif
1395 ms
0100020001023.jpg
1396 ms
0000000010163.jpg
1417 ms
0000000008063.jpg
1444 ms
0000000010133.jpg
1613 ms
0000000009953.jpg
1754 ms
menu.gif
1831 ms
community_menu.gif
1601 ms
is_show_gmo_header.html
1065 ms
sdk.js
8 ms
ga.js
31 ms
__utm.gif
30 ms
111 ms
xd_arbiter.php
40 ms
xd_arbiter.php
50 ms
page.php
516 ms
WyrBmrPZm7I.css
39 ms
DJnYq9lShV8.css
62 ms
drXqyuWvz8i.css
87 ms
RB2eiK1mfi1.css
49 ms
qwhOBnbs1z3.css
40 ms
wuJpCQvW7MO.css
50 ms
Pe827peo11F.css
71 ms
XQb5WMD0OUK.css
72 ms
q68gy-v_YMF.js
75 ms
ehA1CqzHyzE.js
78 ms
0wM5s1Khldu.js
76 ms
1bNoFZUdlYZ.js
76 ms
njO1TPvGzoR.js
73 ms
OloiM1PZafe.js
75 ms
LTv6ZK-5zxz.js
121 ms
1FCa-btixu2.js
79 ms
Oagsvfb4VWi.js
79 ms
pObvZSrFc_4.js
79 ms
Kt4tkgSRvHH.js
79 ms
H3EKDTObx05.js
119 ms
eR-qA8bp1RM.js
117 ms
1QuX41zDRrx.js
159 ms
10264976_600277420105375_2247514239163041127_n.jpg
261 ms
safe_image.php
210 ms
11025710_643607049105745_6445880188878507183_n.jpg
39 ms
12552532_964726880273136_6820661007841792109_n.jpg
39 ms
1173850_496710813751711_150300382_n.jpg
44 ms
10400744_494759280719876_4759765584430866422_n.jpg
44 ms
12088002_10156158898155442_4817635241922785111_n.jpg
112 ms
10406952_722095734516542_4178336891375163617_n.jpg
53 ms
11986408_988666377861616_8898135058099324373_n.jpg
52 ms
12342579_947484045328074_1186910441137578270_n.jpg
52 ms
63199_177275368962278_5983335_n.jpg
54 ms
12360012_123649788004044_3739185130297103371_n.jpg
159 ms
12003364_1045985055421236_8941257665227066344_n.jpg
53 ms
12734121_127706924286199_3381363035891116534_n.jpg
53 ms
12661812_906349742814037_6375095240234469052_n.jpg
55 ms
12717350_946932915402295_3295973494284602063_n.jpg
55 ms
1913939_807435822722866_4059027083245768729_n.jpg
56 ms
12734062_797395377060244_3803262017327306607_n.jpg
70 ms
12715741_797397657060016_431768409155413822_n.jpg
74 ms
12743695_797398050393310_5269997989235162303_n.jpg
106 ms
12733993_797398167059965_4757713041310675520_n.jpg
190 ms
1378790_1465655230326201_1548544793_n.jpg
86 ms
12670104_790849491048166_5950754856370005001_n.jpg
86 ms
12651107_790435547756227_3662177137740991247_n.jpg
103 ms
12670235_790435617756220_1330519660589236366_n.jpg
154 ms
12592415_790435761089539_5621477169633192270_n.jpg
103 ms
12651323_790436047756177_5349111382964747793_n.jpg
105 ms
wL6VQj7Ab77.png
28 ms
s7jcwEQH7Sx.png
27 ms
QDwYpIaRyfG.png
27 ms
K00K-UgnsKu.png
26 ms
gxbPuQdXIZP.png
26 ms
I6-MnjEovm5.js
8 ms
pQrUxxo5oQp.js
8 ms
nocto.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
nocto.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
nocto.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Nocto.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 Nocto.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.
nocto.jp
Open Graph description is not detected on the main page of Nocto. 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: