11 sec in total
1.9 sec
8.8 sec
290 ms
Click here to check amazing Spark Auckland content for New Zealand. Otherwise, check out these important facts you probably never knew about spark.auckland.ac.nz
Visit spark.auckland.ac.nzWe analyzed Spark.auckland.ac.nz page load time and found that the first response time was 1.9 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
spark.auckland.ac.nz performance score
1875 ms
1175 ms
1725 ms
1105 ms
960 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Spark.auckland.ac.nz, 81% (62 requests) were made to Velocity.auckland.ac.nz and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Spark.auckland.ac.nz.
Page size can be reduced by 1.3 MB (61%)
2.2 MB
862.2 kB
In fact, the total size of Spark.auckland.ac.nz main page is 2.2 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. 55% of websites need less resources to load. Javascripts take 833.7 kB which makes up the majority of the site volume.
Potential reduce by 109.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 19.1 kB, which is 15% 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 109.8 kB or 84% of the original size.
Potential reduce by 25.0 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. Spark Auckland images are well optimized though.
Potential reduce by 616.7 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 616.7 kB or 74% of the original size.
Potential reduce by 584.7 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. Spark.auckland.ac.nz needs all CSS files to be minified and compressed as it can save up to 584.7 kB or 84% of the original size.
Number of requests can be reduced by 38 (58%)
66
28
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spark Auckland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
spark.auckland.ac.nz
1875 ms
www.spark.auckland.ac.nz
1175 ms
www.velocity.auckland.ac.nz
1725 ms
www.velocity.auckland.ac.nz
1105 ms
default.css
960 ms
SearchSkinObjectPreview.css
391 ms
module.css
763 ms
module.css
389 ms
portal.css
588 ms
ListView_Slider.css
770 ms
jquery.min.js
33 ms
jquery-migrate-1.2.1.min.js
4 ms
jquery-ui.min.js
55 ms
skin.css
582 ms
layerslider.css
750 ms
base.min.css
1560 ms
WebForms.js
57 ms
jquery.easing.js
412 ms
jquery-transit-modified.js
750 ms
layerslider.transitions.js
629 ms
jquerytransit.js
759 ms
layerslider.kreaturamedia.jquery.js
798 ms
sliderview.js
781 ms
menu.min.js
792 ms
MicrosoftAjax.js
82 ms
MicrosoftAjaxWebForms.js
106 ms
dnn.js
941 ms
dnn.js
947 ms
dnn.xml.js
971 ms
dnn.xml.jsparser.js
981 ms
dnn.xmlhttp.js
987 ms
dnn.xmlhttp.jsxmlhttprequest.js
1131 ms
dnn.modalpopup.js
1138 ms
dnn.servicesframework.js
1160 ms
SearchSkinObjectPreview.js
1181 ms
dnncore.js
1177 ms
css
26 ms
js
50 ms
base.js
1828 ms
VelocityTheme_Inner.js
1175 ms
VelocityTheme_Inner.theme.css
1181 ms
initWidgets.js
1182 ms
base-1.min.css
400 ms
HeaderLogoSmall.png
201 ms
Banner-1.jpg
208 ms
buttonRSVPhere.png
202 ms
Speaker.jpg
581 ms
buttonVelocityRSVP.png
204 ms
SliderHome1.jpg
994 ms
LogoUniServicesSLIDER.png
485 ms
LogoROSSLIDER.png
483 ms
LogoATEEDASLIDER.png
484 ms
LogoVelocityOrangeSmall.png
595 ms
logoCircleOrange.png
627 ms
LogoIcehouse.png
629 ms
LogoUABS.png
630 ms
LogoUniServices.png
782 ms
LogoROS2.png
802 ms
LogoATEEDA.png
850 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
7 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
27 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
28 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
27 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
27 ms
social-sprites.png
781 ms
parallax-image.jpg
965 ms
fontawesome-webfont.woff
1086 ms
fontawesome-webfont.woff
918 ms
DotNetNukeAjaxShared.js
526 ms
skin.css
524 ms
Paul%20Cameron.jpg
842 ms
LogoVelocityGreySmall.png
655 ms
nologo.png
675 ms
nextpage.png
731 ms
prevpage.png
732 ms
widgets.js
333 ms
skin.png
198 ms
spark.auckland.ac.nz SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spark.auckland.ac.nz 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 Spark.auckland.ac.nz 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.
spark.auckland.ac.nz
Open Graph description is not detected on the main page of Spark Auckland. 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: