1.8 sec in total
36 ms
1.6 sec
164 ms
Welcome to openair.com homepage info - get ready to check Open Air best content for United States right away, or after learning these important things about openair.com
NetSuite OpenAir helps improve invoicing accuracy and revenue recognition and increase visibility into your services organization.
Visit openair.comWe analyzed Openair.com page load time and found that the first response time was 36 ms and then it took 1.7 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.
openair.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value5.5 s
19/100
25%
Value6.4 s
41/100
10%
Value70 ms
99/100
30%
Value2.027
0/100
15%
Value5.7 s
68/100
10%
36 ms
467 ms
29 ms
30 ms
31 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 43% of them (33 requests) were addressed to the original Openair.com, 53% (40 requests) were made to Nsportal.openair.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (769 ms) relates to the external source Nsportal.openair.com.
Page size can be reduced by 21.2 kB (5%)
456.4 kB
435.3 kB
In fact, the total size of Openair.com main page is 456.4 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. 25% of websites need less resources to load. Images take 394.9 kB which makes up the majority of the site volume.
Potential reduce by 14.8 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 3.7 kB, which is 19% 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 14.8 kB or 76% of the original size.
Potential reduce by 6.1 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. Open Air images are well optimized though.
Potential reduce by 198 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.
Number of requests can be reduced by 31 (74%)
42
11
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Air. 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.
openair.com
36 ms
www.openair.com
467 ms
font-basic.css
29 ms
menu.css
30 ms
megamenu.css
31 ms
layout-oa.css
32 ms
colorbox.css
31 ms
NLPortal.js
41 ms
jquery-1.11.3.min.js
43 ms
tabs.js
40 ms
swfobject.js
41 ms
utils.js
42 ms
loopedslider.js
54 ms
cufon-yui.js
55 ms
jquery.featureList-1.0.0.js
57 ms
jquery.megamenu.js
59 ms
jquery.megamenu.set.js
61 ms
jquery.easing.1.2.js
66 ms
jquery.easing.1.2.expand.set.js
66 ms
roundabout.js
67 ms
roundabout_shapes.js
69 ms
jquery-ui-1.8.5.custom.min.js
67 ms
NetSuiteTracker.js
79 ms
font-basic.css
186 ms
menu.css
177 ms
megamenu.css
171 ms
layout-oa.css
194 ms
colorbox.css
175 ms
NLPortal.js
252 ms
tabs.js
268 ms
swfobject.js
265 ms
utils.js
265 ms
jquery-1.11.3.min.js
428 ms
loopedslider.js
257 ms
cufon-yui.js
347 ms
jquery.featureList-1.0.0.js
348 ms
jquery.megamenu.js
328 ms
jquery.megamenu.set.js
332 ms
jquery.easing.1.2.js
337 ms
jquery.easing.1.2.expand.set.js
432 ms
roundabout.js
432 ms
jquery-ui-1.8.5.custom.min.js
431 ms
roundabout_shapes.js
431 ms
NetSuiteTracker.js
439 ms
sitebackground.jpg
769 ms
ns-oa-logo.jpg
22 ms
top-right-bg.gif
89 ms
btn-green.gif
20 ms
top-phone-oa.png
21 ms
brn-960x280-srp.jpg
21 ms
dgram_wheel.jpg
21 ms
free-trial.png
21 ms
see-demo.png
29 ms
openair-salesforce.jpg
30 ms
spacer.gif
30 ms
PostBullets.png
94 ms
tabBGRndCrnr.gif
95 ms
dgram_wheel_rt.jpg
93 ms
dgram_wheel.jpg
253 ms
tabboxbtm.gif
158 ms
cv_asideinnerboxtop_220x10.png
187 ms
cv_asideinnerboxbt_220x10.png
179 ms
bt-960x30.png
183 ms
ns-oa-logo.jpg
243 ms
btn-green.gif
270 ms
top-phone-oa.png
273 ms
brn-960x280-srp.jpg
585 ms
dgram_wheel.jpg
445 ms
free-trial.png
339 ms
see-demo.png
344 ms
openair-salesforce.jpg
478 ms
spacer.gif
420 ms
ga.js
28 ms
tracker.nl
16 ms
__utm.gif
12 ms
roundtrip.js
10 ms
openair.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.
openair.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
Issues were logged in the Issues panel in Chrome Devtools
openair.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Openair.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 Openair.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.
openair.com
Open Graph description is not detected on the main page of Open Air. 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: