2.1 sec in total
279 ms
877 ms
920 ms
Welcome to iex.com homepage info - get ready to check Iex best content right away, or after learning these important things about iex.com
Build relationships that last with the only AI purpose-built platform for customer experience (CX)
Visit iex.comWe analyzed Iex.com page load time and found that the first response time was 279 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
iex.com performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value4.9 s
28/100
25%
Value11.6 s
4/100
10%
Value8,640 ms
0/100
30%
Value0.014
100/100
15%
Value26.8 s
0/100
10%
279 ms
8 ms
234 ms
13 ms
17 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Iex.com, 98% (128 requests) were made to Nice.com and 2% (2 requests) were made to Resources.nice.com. The less responsive or slowest element that took the longest time to load (279 ms) belongs to the original domain Iex.com.
Page size can be reduced by 177.7 kB (43%)
416.5 kB
238.8 kB
In fact, the total size of Iex.com main page is 416.5 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. 60% of websites need less resources to load. HTML takes 216.4 kB which makes up the majority of the site volume.
Potential reduce by 177.7 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 177.7 kB or 82% of the original size.
Potential reduce by 3 B
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. Iex images are well optimized though.
Number of requests can be reduced by 39 (30%)
128
89
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
iex.com
279 ms
www.nice.com
8 ms
www.nice.com
234 ms
550c1f703c58e604.css
13 ms
7c7e028147a5c0d6.css
17 ms
f8dc5a8abf10bfdc.css
13 ms
dcdc84af85f93fa2.css
16 ms
b622b044c5460088.css
12 ms
46d2f1b70d0e73f2.css
22 ms
2e85c571399b9690.css
20 ms
ed1e46b13721ba42.css
18 ms
5eb27379a0ba8146.css
20 ms
9bc1ffd3896e0178.css
22 ms
7596bd1125c0dc86.css
23 ms
d0abf6b22f164312.css
23 ms
cdc38ee519b5d126.css
23 ms
fd9d1056-c58c9c3d6562e869.js
28 ms
4429-2ce8b0c609a5476a.js
25 ms
3727-63be67f86b747599.js
28 ms
3452-973528faf84bb69d.js
25 ms
4444-ecb0a375b063b179.js
29 ms
6633-9d1b10cea6d716d0.js
29 ms
main-app-885a59cc6dcc11fe.js
28 ms
error-50815ea40f34b759.js
30 ms
4516-704b93a63069d38f.js
30 ms
231-c50aab89f71c1932.js
30 ms
5223-a94d0f5d8616105b.js
30 ms
5594-380624e205795a0e.js
30 ms
layout-1c8fb26f612670ce.js
121 ms
728-b4eccbc786573355.js
30 ms
page-b95f58462240d28b.js
31 ms
polyfills-42372ed130431b0a.js
38 ms
webpack-4f7ee2d22fddad72.js
27 ms
geometric-background.png
35 ms
84e46dcd4764448c.css
11 ms
03b734b4cbf3fde9.css
11 ms
image
21 ms
chevron-right.svg
139 ms
420pxGlobeiconsvg.png
132 ms
linkedin.svg
125 ms
x.svg
133 ms
fb.svg
136 ms
youtube.svg
143 ms
image
126 ms
image
128 ms
image
128 ms
image
131 ms
image
140 ms
image
134 ms
image
137 ms
image
138 ms
image
142 ms
image
146 ms
image
144 ms
image
142 ms
image
144 ms
image
145 ms
image
147 ms
image
146 ms
image
146 ms
image
146 ms
image
149 ms
image
147 ms
image
148 ms
image
148 ms
image
149 ms
image
151 ms
image
149 ms
two-column-full-width-background-2760x858-1.jpg
22 ms
image
148 ms
7d73a16e4cbeab9d.css
137 ms
image
149 ms
image
147 ms
image
139 ms
image
44 ms
image
43 ms
image
42 ms
image
42 ms
image
38 ms
image
40 ms
image
37 ms
image
36 ms
image
36 ms
image
33 ms
image
33 ms
image
32 ms
image
31 ms
image
31 ms
image
30 ms
image
30 ms
image
29 ms
chevron-right.svg
121 ms
image
34 ms
image
35 ms
image
35 ms
image
34 ms
image
34 ms
image
35 ms
image
35 ms
image
35 ms
image
36 ms
73a489ddd79ac56a.css
6 ms
image
13 ms
image
12 ms
image
13 ms
image
12 ms
image
13 ms
image
13 ms
image
14 ms
image
14 ms
image
15 ms
image
15 ms
image
14 ms
image
14 ms
image
15 ms
image
16 ms
image
15 ms
image
15 ms
image
15 ms
image
17 ms
image
17 ms
image
17 ms
image
16 ms
image
17 ms
image
17 ms
image
18 ms
c4807710ef4d199b.css
12 ms
734022d315be6e35.css
3 ms
image
20 ms
image
11 ms
image
6 ms
iex.com 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
Image elements do not have [alt] attributes
iex.com 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
Browser errors were logged to the console
Page has valid source maps
iex.com 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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iex.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Iex.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.
iex.com
Open Graph data is detected on the main page of Iex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: