4.1 sec in total
1.1 sec
2.8 sec
207 ms
Visit iweiss.com now to see the best up-to-date IWEISS content for United States and also check out these interesting facts you probably never knew about iweiss.com
Discover IWEISS, your one-stop destination for premium fabric, drapery, curtain tracks, and rigging systems. 120 years of excellence, serving customers nationwide and worldwide.
Visit iweiss.comWe analyzed Iweiss.com page load time and found that the first response time was 1.1 sec and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
iweiss.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value9.2 s
1/100
25%
Value13.7 s
2/100
10%
Value1,340 ms
17/100
30%
Value0.11
87/100
15%
Value18.6 s
3/100
10%
1061 ms
21 ms
445 ms
10 ms
16 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 52% of them (42 requests) were addressed to the original Iweiss.com, 14% (11 requests) were made to Demo.a2zinc.net and 5% (4 requests) were made to Libs.a2zinc.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Iweiss.com.
Page size can be reduced by 276.6 kB (27%)
1.0 MB
757.1 kB
In fact, the total size of Iweiss.com main page is 1.0 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. 40% of websites need less resources to load. Images take 695.6 kB which makes up the majority of the site volume.
Potential reduce by 19.5 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 19.5 kB or 71% of the original size.
Potential reduce by 27.7 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. IWEISS images are well optimized though.
Potential reduce by 143.2 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 143.2 kB or 69% of the original size.
Potential reduce by 86.2 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. Iweiss.com needs all CSS files to be minified and compressed as it can save up to 86.2 kB or 84% of the original size.
Number of requests can be reduced by 36 (46%)
78
42
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IWEISS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.iweiss.com
1061 ms
buttons.js
21 ms
jquery-ui-1.8.22.custom.css
445 ms
jquery.min.js
10 ms
jquery-ui.min.js
16 ms
jquery-migrate-1.2.1.min.js
10 ms
jquery.mousewheel-3.0.4.pack.js
184 ms
jquery.fancybox-1.3.4.pack.js
356 ms
jquery.fancybox-1.3.4.css
299 ms
fadein.js
203 ms
jQueryUI.js
361 ms
cms.js
304 ms
css.src
740 ms
a2zWidget.js
82 ms
ready.js
143 ms
ga.js
31 ms
masthead.png
179 ms
98.jpg
272 ms
97.jpg
360 ms
96.jpg
212 ms
94.jpg
360 ms
93.jpg
312 ms
92.jpg
456 ms
91.jpg
406 ms
90.jpg
455 ms
89.jpg
610 ms
88.jpg
537 ms
87.jpg
628 ms
86.jpg
607 ms
85.jpg
633 ms
84.jpg
631 ms
83.jpg
740 ms
spotlightBack.jpg
707 ms
newsletterBar.png
709 ms
stageDemo.png
739 ms
604-1-t.jpg
740 ms
etcp.png
742 ms
usitt.png
807 ms
tcg.png
809 ms
historic.png
804 ms
facebook.png
807 ms
twitter.png
810 ms
youtube.png
823 ms
linkedin.png
895 ms
pinterest.png
911 ms
instagram.png
898 ms
ExhibitorBadge.aspx
659 ms
__utm.gif
97 ms
getAllAppDefault.esi
50 ms
loading.gif
765 ms
getSegment.php
140 ms
checkOAuth.esi
46 ms
t.dhj
44 ms
t.dhj
31 ms
cm
29 ms
s-3271.xgi
33 ms
hbpix
38 ms
xrefid.xgi
4 ms
7 ms
7 ms
pixel
18 ms
pixel
15 ms
2981
20 ms
Default.css
70 ms
jquery-1.6.1.js
6 ms
a2zAnalytics.js
90 ms
aaw_topleft.png
103 ms
aaw_logo.png
90 ms
aaw_top.png
100 ms
aaw_topright.png
99 ms
aaw_left.png
101 ms
AddToExpoPlan.png
137 ms
ViewExpoPlan.png
136 ms
RegisterNow.png
133 ms
aaw_right.png
135 ms
aaw_bottomleft.png
134 ms
aaw_bottom.png
136 ms
aaw_bottomright.png
169 ms
TrackExpoBadgeView
318 ms
IsBoothInExpoPlan
196 ms
print.css
92 ms
iweiss.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.
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
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.
iweiss.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
iweiss.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Iweiss.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 Iweiss.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.
iweiss.com
Open Graph description is not detected on the main page of IWEISS. 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: