2.4 sec in total
187 ms
1.8 sec
461 ms
Welcome to annualreport.uli.org homepage info - get ready to check Annual Report ULI best content for United States right away, or after learning these important things about annualreport.uli.org
Visit annualreport.uli.orgWe analyzed Annualreport.uli.org page load time and found that the first response time was 187 ms and then it took 2.2 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.
annualreport.uli.org performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value2.7 s
85/100
25%
Value5.0 s
64/100
10%
Value910 ms
31/100
30%
Value0.416
23/100
15%
Value14.3 s
9/100
10%
187 ms
237 ms
830 ms
24 ms
36 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Annualreport.uli.org, 90% (56 requests) were made to Uli.org and 2% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (830 ms) relates to the external source Cdnjs.cloudflare.com.
Page size can be reduced by 75.4 kB (1%)
5.1 MB
5.0 MB
In fact, the total size of Annualreport.uli.org main page is 5.1 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. Only a small number of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 71.1 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 14.4 kB, which is 17% 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 71.1 kB or 84% of the original size.
Potential reduce by 0 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. Annual Report ULI images are well optimized though.
Potential reduce by 114 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 4.1 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. Annualreport.uli.org needs all CSS files to be minified and compressed as it can save up to 4.1 kB or 11% of the original size.
Number of requests can be reduced by 27 (71%)
38
11
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Annual Report ULI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
annualreport.uli.org
187 ms
237 ms
polyfill.min.js
830 ms
global.css
24 ms
global.css
36 ms
global-nav.css
32 ms
style.min.css
55 ms
styles.css
41 ms
uli-sso-plugin.css
44 ms
default.css
34 ms
tablepress-responsive.min.css
47 ms
pintra-redirect.js
52 ms
email-decode.min.js
37 ms
styles.css
47 ms
styles.css
49 ms
styles.css
60 ms
styles.css
59 ms
styles.css
58 ms
wp-polyfill-inert.min.js
67 ms
regenerator-runtime.min.js
63 ms
wp-polyfill.min.js
70 ms
hooks.min.js
69 ms
i18n.min.js
95 ms
index.js
77 ms
index.js
76 ms
app.js
85 ms
app.js
80 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
58 ms
gtm.js
172 ms
uli-square-logo.png
88 ms
icons.svg
83 ms
tool-icon-knowledge-finder.svg
85 ms
tool-icon-member-directory.svg
86 ms
tool-icon-navigator.svg
82 ms
uli-square-tagline-318x168.png
83 ms
ULI-2023-Annual-Report.png
116 ms
Download-Now.jpg
91 ms
uli-square-tagline.png
109 ms
normal.woff2
42 ms
normal.woff2
90 ms
normal.woff2
90 ms
normal.woff2
80 ms
normal.woff2
80 ms
normal.woff2
174 ms
normal.woff2
80 ms
normal.woff2
141 ms
normal.woff2
104 ms
normal.woff2
174 ms
normal.woff2
185 ms
normal.woff2
165 ms
normal.woff2
186 ms
normal.woff2
231 ms
normal.woff2
212 ms
normal.woff2
212 ms
normal.woff2
213 ms
normal.woff2
212 ms
normal.woff2
212 ms
normal.woff2
224 ms
normal.woff2
224 ms
load
86 ms
header-bg-xl.jpg
388 ms
tinypass.min.js
83 ms
annualreport.uli.org accessibility score
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
annualreport.uli.org 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
annualreport.uli.org 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Annualreport.uli.org 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 Annualreport.uli.org 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.
annualreport.uli.org
Open Graph description is not detected on the main page of Annual Report ULI. 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: