2.7 sec in total
143 ms
1.7 sec
827 ms
Click here to check amazing Native Script content for India. Otherwise, check out these important facts you probably never knew about nativescript.org
Build truly native iOS, Android and Windows Phone apps with Javascript and CSS. Try NativeScript open-source framework for cross-platform development.
Visit nativescript.orgWe analyzed Nativescript.org page load time and found that the first response time was 143 ms and then it took 2.5 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.
nativescript.org performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value2.9 s
79/100
25%
Value3.0 s
94/100
10%
Value490 ms
59/100
30%
Value0.002
100/100
15%
Value4.5 s
82/100
10%
143 ms
213 ms
63 ms
156 ms
86 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 10% of them (5 requests) were addressed to the original Nativescript.org, 12% (6 requests) were made to Ajax.aspnetcdn.com and 10% (5 requests) were made to Buttons.github.io. The less responsive or slowest element that took the longest time to load (998 ms) belongs to the original domain Nativescript.org.
Page size can be reduced by 727.1 kB (27%)
2.7 MB
1.9 MB
In fact, the total size of Nativescript.org main page is 2.7 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. 50% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 33.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 33.5 kB or 72% of the original size.
Potential reduce by 22.8 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. Native Script images are well optimized though.
Potential reduce by 404.8 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 404.8 kB or 62% of the original size.
Potential reduce by 265.9 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. Nativescript.org needs all CSS files to be minified and compressed as it can save up to 265.9 kB or 81% of the original size.
Number of requests can be reduced by 25 (64%)
39
14
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Native Script. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
nativescript.org
143 ms
www.nativescript.org
213 ms
Telerik.Web.UI.WebResource.axd
63 ms
css
156 ms
style.min.css
86 ms
WebForms.js
160 ms
MicrosoftAjax.js
215 ms
MicrosoftAjaxWebForms.js
266 ms
jquery-1.9.1.min.js
324 ms
jquery-1.8.3.min.js
362 ms
Telerik.Web.UI.WebResource.axd
193 ms
jQuery.Validate.min.js
307 ms
all.js
96 ms
gtm.js
117 ms
sharing.png
103 ms
showcases-cool-examples.png
106 ms
showcases-cool-examples.png
998 ms
analytics.js
222 ms
I3_ZnWTj-NA
309 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
224 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
247 ms
ns-icons.woff
72 ms
dual-600.woff
72 ms
sdk.js
157 ms
buttons.js
228 ms
widgets.js
244 ms
collect
117 ms
collect
265 ms
elqCfg.min.js
226 ms
prum.min.js
210 ms
269 ms
www-embed-player-vflQrT_sR.css
250 ms
www-embed-player.js
326 ms
xd_arbiter.php
145 ms
buttons.css
94 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
77 ms
NativeScript
102 ms
svrGP
370 ms
ga-audiences
154 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
68 ms
info.json
144 ms
buttons.html
25 ms
octicons.css
9 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
33 ms
ad_status.js
117 ms
octicons.woff
14 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
72 ms
jot
94 ms
svrGP.aspx
76 ms
nativescript.org 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.
nativescript.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
nativescript.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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nativescript.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Nativescript.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.
nativescript.org
Open Graph data is detected on the main page of Native Script. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: