2.9 sec in total
36 ms
2.6 sec
264 ms
Click here to check amazing NAIOP content for United States. Otherwise, check out these important facts you probably never knew about naiop.org
Visit naiop.orgWe analyzed Naiop.org page load time and found that the first response time was 36 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
naiop.org performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value14.9 s
0/100
25%
Value7.3 s
29/100
10%
Value1,560 ms
13/100
30%
Value0.058
98/100
15%
Value12.5 s
14/100
10%
36 ms
1377 ms
23 ms
32 ms
34 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 68% of them (42 requests) were addressed to the original Naiop.org, 6% (4 requests) were made to F.vimeocdn.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Naiop.org.
Page size can be reduced by 603.3 kB (47%)
1.3 MB
679.0 kB
In fact, the total size of Naiop.org main page is 1.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 590.9 kB which makes up the majority of the site volume.
Potential reduce by 57.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 23.1 kB, which is 33% 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 57.3 kB or 82% of the original size.
Potential reduce by 93.2 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. Obviously, NAIOP needs image optimization as it can save up to 93.2 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 302.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 302.2 kB or 68% of the original size.
Potential reduce by 150.6 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. Naiop.org needs all CSS files to be minified and compressed as it can save up to 150.6 kB or 85% of the original size.
Number of requests can be reduced by 26 (45%)
58
32
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NAIOP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
naiop.org
36 ms
www.naiop.org
1377 ms
VisitorIdentification.js
23 ms
shared.css
32 ms
home.css
34 ms
font-awesome.min.css
8 ms
jquery-1.11.2.min.js
14 ms
jquery.sudoSlider.min.js
60 ms
utils.js
65 ms
home.js
64 ms
gtm.js
124 ms
151076160
152 ms
logo.png
82 ms
input-bg.png
86 ms
input-go.png
86 ms
subnav-carat.png
84 ms
callout-arrow.png
85 ms
shopping-cart.png
91 ms
pipe-login.png
91 ms
ICON16_PROJECTS5_960x385.ashx
109 ms
DOY_2015%20Majestic4.ashx
1108 ms
National%20Forums02_960x385.ashx
109 ms
Education_OnlineCourses2_960x385%20(2).ashx
610 ms
AshleyPowellChairman16_.ashx
624 ms
NAIOP_CenterEduc_Logo_4C.ashx
128 ms
ICON-impactProjects-horizontal.ashx
659 ms
centerpointproperties.ashx
166 ms
Jones%20Lang%20Lasalle.ashx
176 ms
Avison_Young_logo.ashx
204 ms
cbre.ashx
196 ms
prologis.ashx
280 ms
usaarealestatecompany.ashx
279 ms
footer-bg.jpg
281 ms
footer-pipe.gif
281 ms
soty_crop.png
304 ms
facebook.ashx
303 ms
twitter.ashx
308 ms
linkedin.ashx
312 ms
google.ashx
325 ms
rss.ashx
330 ms
youtube.ashx
340 ms
researchicon.ashx
350 ms
magazineicon.ashx
356 ms
connecticon.ashx
377 ms
1123.js
29 ms
TradeGothicLTStd-Bold.woff
293 ms
fontawesome-webfont.woff
28 ms
analytics.js
28 ms
fbds.js
60 ms
player.js
95 ms
player.css
80 ms
ga.js
153 ms
vuid.min.js
94 ms
collect
29 ms
collect
133 ms
145 ms
proxy.html
57 ms
550725753.jpg
88 ms
9552787_60x60.jpg
57 ms
__utm.gif
19 ms
print-homepage.css
10 ms
22 ms
naiop.org 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 match their roles
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
naiop.org 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
Page has valid source maps
naiop.org 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
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 Naiop.org 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 Naiop.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.
naiop.org
Open Graph description is not detected on the main page of NAIOP. 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: