13.4 sec in total
535 ms
9.9 sec
3 sec
Click here to check amazing Necoichi content for Taiwan. Otherwise, check out these important facts you probably never knew about necoichi.tw
來自日本的猫壱 為貓咪用品專用品牌 猫壱的logo包含最初的想法和決心 “對貓來說是第一,貓是第一” 用簡單而美麗的方式來實現貓和人一起相處的生活。
Visit necoichi.twWe analyzed Necoichi.tw page load time and found that the first response time was 535 ms and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
necoichi.tw performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value35.4 s
0/100
25%
Value14.2 s
1/100
10%
Value1,860 ms
9/100
30%
Value0.246
50/100
15%
Value26.1 s
0/100
10%
535 ms
1327 ms
119 ms
157 ms
120 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Necoichi.tw, 42% (49 requests) were made to Img-shoplineapp-com.s3.amazonaws.com and 17% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source Img-shoplineapp-com.s3.amazonaws.com.
Page size can be reduced by 1.0 MB (6%)
17.2 MB
16.2 MB
In fact, the total size of Necoichi.tw main page is 17.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. 85% 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 16.4 MB which makes up the majority of the site volume.
Potential reduce by 87.3 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 16.2 kB, which is 15% 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 87.3 kB or 82% of the original size.
Potential reduce by 421.0 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. Necoichi images are well optimized though.
Potential reduce by 164.6 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 164.6 kB or 58% of the original size.
Potential reduce by 371.0 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. Necoichi.tw needs all CSS files to be minified and compressed as it can save up to 371.0 kB or 83% of the original size.
Number of requests can be reduced by 36 (33%)
110
74
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Necoichi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
necoichi.tw
535 ms
www.necoichi.tw
1327 ms
css
119 ms
css
157 ms
application-85b2edfdc81c48a40be7829cd2d3d61f.css
120 ms
slate.css
451 ms
currencies.js
148 ms
application-8334f56d35128be1d2b93f5bae85b62a.js
161 ms
css
72 ms
proxy
871 ms
original.png
3318 ms
wqdlWn4mOM4
329 ms
card_allpay.png
1439 ms
mixpanel-2.2.min.js
345 ms
analytics.js
284 ms
fbds.js
360 ms
fbevents.js
457 ms
events
546 ms
cart
391 ms
transparent_xlarge.png
205 ms
original.jpg
1753 ms
original.jpg
2414 ms
original.jpg
2208 ms
original.jpg
2645 ms
original.jpg
1821 ms
original.jpg
3083 ms
original.jpg
2502 ms
original.jpg
3543 ms
original.jpg
3743 ms
original.jpg
3393 ms
original.jpg
4848 ms
original.jpg
3539 ms
original.jpg
3985 ms
transparent_xlarge.png
4771 ms
original.png
6188 ms
original.png
4871 ms
original.png
5504 ms
original.jpg
4446 ms
original.jpg
4917 ms
transparent_xlarge.png
5235 ms
transparent_xlarge.png
5317 ms
transparent_xlarge.png
5336 ms
transparent_xlarge.png
5388 ms
original.jpg
5482 ms
transparent_xlarge.png
5791 ms
transparent_xlarge.png
5802 ms
transparent_xlarge.png
5859 ms
transparent_xlarge.png
5956 ms
transparent_xlarge.png
5766 ms
original.jpg
6011 ms
original.jpg
6032 ms
original.jpg
6245 ms
original.jpg
6304 ms
transparent_xlarge.png
6428 ms
transparent_xlarge.png
6270 ms
logo-powered-by-dark.png
936 ms
likebox.php
251 ms
~text
118 ms
fontawesome-webfont.woff
105 ms
www-embed-player-vflQrT_sR.css
142 ms
www-embed-player.js
183 ms
collect
60 ms
collect
78 ms
10 ms
collect
107 ms
8 ms
11 ms
ga-audiences
82 ms
54 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
42 ms
ad_status.js
68 ms
C-D3sjGKj3j.css
293 ms
zEMlMNmIXUJ.css
362 ms
rlRTaLkHnJA.css
433 ms
_rx8naC75Dy.js
632 ms
b94UUzHjapV.js
660 ms
0wM5s1Khldu.js
504 ms
TTCre3391I0.js
503 ms
ezSeJz80WmZ.js
710 ms
6kb4qPGfoPa.js
568 ms
Xq6IQFjERmT.js
569 ms
-YBL9NxImsH.js
659 ms
-AWXRi4rrMJ.js
677 ms
B9x7unvN8Hn.js
705 ms
DULOQLY-aiv.js
701 ms
VpVLc1dkyZp.js
767 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
67 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
79 ms
events
514 ms
12565465_1113418715376259_8118148019349235186_n.jpg
332 ms
10653551_840242636027203_2699945261085975683_n.jpg
397 ms
12651359_1032038986818682_5436833268947622343_n.jpg
491 ms
64937_164984533517285_3992053_n.jpg
564 ms
12744061_10201374943972780_5956713961407193091_n.jpg
722 ms
12512465_1138529376187185_8033900985653145527_n.jpg
609 ms
11666211_1191954917496802_7806006607281719505_n.jpg
539 ms
11233518_999152326770394_1140438940321409385_n.jpg
537 ms
12494665_813398065452857_8576366748136566361_n.jpg
560 ms
wL6VQj7Ab77.png
127 ms
s7jcwEQH7Sx.png
127 ms
355OzDqhgUf.png
73 ms
transparent_xlarge.png
4762 ms
original.jpg
4618 ms
I6-MnjEovm5.js
71 ms
f6T91Deal_q.js
134 ms
original.jpg
4548 ms
transparent_xlarge.png
4126 ms
transparent_xlarge.png
4272 ms
original.png
4273 ms
original.png
3819 ms
original.png
4095 ms
original.png
3604 ms
transparent_xlarge.png
3683 ms
transparent_xlarge.png
3708 ms
original.png
3390 ms
original.png
3395 ms
nr-885.min.js
20 ms
necoichi.tw 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
necoichi.tw 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
necoichi.tw 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Necoichi.tw 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 Necoichi.tw 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.
necoichi.tw
Open Graph data is detected on the main page of Necoichi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: