2.4 sec in total
63 ms
1.6 sec
744 ms
Visit ndi.com now to see the best up-to-date NDI content for United States and also check out these interesting facts you probably never knew about ndi.com
NDI faux florals and botanicals are the perfect addition to any space. Come explore our wide variety of quality stems and arrangements.
Visit ndi.comWe analyzed Ndi.com page load time and found that the first response time was 63 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
ndi.com performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value36.2 s
0/100
25%
Value5.5 s
55/100
10%
Value110 ms
98/100
30%
Value0.466
19/100
15%
Value7.4 s
49/100
10%
63 ms
495 ms
118 ms
12 ms
21 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 31% of them (12 requests) were addressed to the original Ndi.com, 38% (15 requests) were made to 54e8458585bd02d810bd-1ae349506755dc090539fb35a11660f8.ssl.cf5.rackcdn.com and 21% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (703 ms) relates to the external source 54e8458585bd02d810bd-1ae349506755dc090539fb35a11660f8.ssl.cf5.rackcdn.com.
Page size can be reduced by 531.1 kB (16%)
3.3 MB
2.8 MB
In fact, the total size of Ndi.com main page is 3.3 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. 45% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 25.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 10.8 kB, which is 35% 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 25.0 kB or 82% of the original size.
Potential reduce by 101.8 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. NDI images are well optimized though.
Potential reduce by 215.1 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 215.1 kB or 67% of the original size.
Potential reduce by 189.3 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. Ndi.com needs all CSS files to be minified and compressed as it can save up to 189.3 kB or 89% of the original size.
Number of requests can be reduced by 4 (15%)
27
23
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NDI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
ndi.com
63 ms
ndi.com
495 ms
ipf0llu.js
118 ms
layout.css
12 ms
jquery.min.js
21 ms
plugins.js
22 ms
main.js
22 ms
ndi.com
167 ms
analytics.js
292 ms
logo.png
89 ms
0b0d9001699b4904d6b7c1c8e771.jpeg
441 ms
cta-light.png
266 ms
btn-callout.png
265 ms
arrow-submit-light.png
265 ms
footerEgg.png
266 ms
ab81f3adeb974e40d08599f005cc.jpeg
385 ms
ffca1f037c80d8dec13c047f25d9.jpeg
373 ms
f5cb4bd221f7ee5af7fa404138b7.jpeg
410 ms
1748ace11113725e87e54d5999d8.jpeg
365 ms
ba5fbcc73edec88c633af09e40fc.jpeg
418 ms
43e6f4fcd6b4190721975df842d7.jpeg
515 ms
e38689b606ce0eddc46f164727da.jpeg
417 ms
c3a71667fc91b200a51a11e58ed7.jpeg
418 ms
ddba0cd47851a3e810bff5d150d1.jpeg
559 ms
cfc68391086630cf8f18c2cdf9ab.jpeg
547 ms
3148bc469637cb055a5c6b86591c.jpeg
703 ms
45f1966d93301849385538ce6c3b.jpeg
512 ms
28652a1ffe5b4566463f1fcb24ad.jpeg
461 ms
custom-orders.jpg
486 ms
hotpoint-products-all-view
397 ms
ypvk_yI2b-_vul5TuOuCZyV2eGRIe_yhSVroliFb0uCffOcREN32IgCjMKM2HMJtgM.woff
78 ms
hCVvsRTUKDJOgMwfK8xY-zXLcnH34Yq5lKzYBDMehvtffOhREN32IgCjMKM2HMJtMb.woff
134 ms
sZqw0BeOokIUXxHaXeJCmT6us5b-fw1GREgUAYifXAqffO0REN32IgCjMKM2HMJtg6.woff
171 ms
iFtCRXuGomJGndf054Mx1oyo2-w8vbrtQykkKmKtBuwffOeREN32IgCjMKM2HMJtg3.woff
196 ms
kpP3Y-bCmjenQmqlpxGQpOkEwd6liPe4LTQf3HlmaK3ff4-gggMdeMJ6Mk6f5Mw.woff
248 ms
D6C_3jl_duovMTYfXgF96e6IMzQ8P_KQ0OP4ntVF0O6ff5WcggMdeMJ6Mk6f5Mb.woff
224 ms
ndicons.ttf
21 ms
p.gif
188 ms
collect
94 ms
ndi.com 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-*] attributes do not have valid values
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
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
ndi.com 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
ndi.com SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ndi.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Ndi.com 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.
ndi.com
Open Graph description is not detected on the main page of NDI. 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: