4.1 sec in total
144 ms
2.8 sec
1.1 sec
Visit aestz.com now to see the best up-to-date Aestz content and also check out these interesting facts you probably never knew about aestz.com
Advanced Engineering solutions
Visit aestz.comWe analyzed Aestz.com page load time and found that the first response time was 144 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
aestz.com performance score
144 ms
1424 ms
171 ms
127 ms
143 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Aestz.com, 85% (52 requests) were made to Aesl.co.tz and 10% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Aesl.co.tz.
Page size can be reduced by 787.4 kB (16%)
5.0 MB
4.2 MB
In fact, the total size of Aestz.com main page is 5.0 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. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 30.9 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 13.1 kB, which is 36% 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 30.9 kB or 85% of the original size.
Potential reduce by 316.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. Aestz images are well optimized though.
Potential reduce by 183.5 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 183.5 kB or 71% of the original size.
Potential reduce by 256.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. Aestz.com needs all CSS files to be minified and compressed as it can save up to 256.9 kB or 87% of the original size.
Number of requests can be reduced by 27 (52%)
52
25
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aestz. 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 17 to 1 for CSS and as a result speed up the page load time.
aestz.com
144 ms
www.aesl.co.tz
1424 ms
bootstrap.css
171 ms
font-awesome.min.css
127 ms
owl.carousel.css
143 ms
owl.theme.css
121 ms
owl.transitions.css
123 ms
lightbox.css
125 ms
style.css
178 ms
light-red.css
195 ms
green.css
200 ms
blue.css
184 ms
light-blue.css
201 ms
yellow.css
221 ms
black.css
233 ms
responsive.css
244 ms
animate.css
251 ms
jquery-2.1.1.min.js
312 ms
bootstrap.min.js
294 ms
modernizr.custom.js
292 ms
owl.carousel.min.js
355 ms
lightbox.min.js
358 ms
jquery.appear.js
357 ms
jquery.fitvids.js
383 ms
jquery.nicescroll.min.js
407 ms
superfish.min.js
386 ms
supersubs.js
400 ms
styleswitcher.js
404 ms
script.js
384 ms
css
26 ms
css
35 ms
close.png
218 ms
loading.gif
217 ms
prev.png
219 ms
next.png
217 ms
logo.jpg
52 ms
project56ae145df23ad.jpg
184 ms
slide56ae4bcecdc47.jpg
481 ms
project56ae148572203.jpg
111 ms
slide56ae181caf8c3.jpg
120 ms
post-1.jpg
234 ms
project56ae489c05370.jpg
307 ms
project56adb3825e423.jpg
331 ms
project56adb53230651.png
419 ms
project56ab61d2e0062jpg
309 ms
project56adb5b1d1d9b.jpg
714 ms
project56ae4aad5d904.jpg
404 ms
project56ab6ee2754cb.jpg
471 ms
project56ae4a6a5e4d9.jpg
572 ms
project56ab6a62b6ecd.jpg
520 ms
project56ab69d4f21eb.jpg
592 ms
project56ab6baf8cfb4.png
643 ms
project56ab6d193b6af.jpg
551 ms
parallax.jpg
584 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
10 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
10 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
11 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
10 ms
fontawesome-webfont.woff
613 ms
HqHm7BVC_nzzTui2lzQTDT8E0i7KZn-EPnyo3HZu7kw.woff
10 ms
-g5pDUSRgvxvOl5u-a_WHw.woff
9 ms
aestz.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aestz.com 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 Aestz.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.
aestz.com
Open Graph description is not detected on the main page of Aestz. 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: