4.2 sec in total
699 ms
3.3 sec
193 ms
Click here to check amazing Azza content for Azerbaijan. Otherwise, check out these important facts you probably never knew about azza.az
Azza Cake House
Visit azza.azWe analyzed Azza.az page load time and found that the first response time was 699 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
azza.az performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value8.0 s
2/100
25%
Value14.5 s
1/100
10%
Value680 ms
44/100
30%
Value0.001
100/100
15%
Value20.4 s
2/100
10%
699 ms
24 ms
36 ms
324 ms
327 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 76% of them (35 requests) were addressed to the original Azza.az, 7% (3 requests) were made to Static.xx.fbcdn.net and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Azza.az.
Page size can be reduced by 530.4 kB (28%)
1.9 MB
1.4 MB
In fact, the total size of Azza.az main page is 1.9 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. 40% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 9.0 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.4 kB, which is 29% 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 9.0 kB or 77% of the original size.
Potential reduce by 185.7 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, Azza needs image optimization as it can save up to 185.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 177.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 177.7 kB or 66% of the original size.
Potential reduce by 157.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. Azza.az needs all CSS files to be minified and compressed as it can save up to 157.9 kB or 86% of the original size.
Number of requests can be reduced by 22 (52%)
42
20
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Azza. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
azza.az
699 ms
css
24 ms
css
36 ms
font-awesome.min.css
324 ms
quick_newsletter.css
327 ms
skin.css
327 ms
layerslider.css
486 ms
colorbox.css
327 ms
bootstrap.2.1.css
485 ms
responsive.css
482 ms
color-01.css
482 ms
style.css
1123 ms
jquery.js
996 ms
jquery.jcarousel.min.js
637 ms
layerslider.kreaturamedia.jquery.js
994 ms
layerslider.transitions.js
799 ms
jquery-easing-1.3.js
639 ms
jquery-transit-modified.js
797 ms
quick_newsletter.js
800 ms
jquery.colorbox.js
1183 ms
custom.js
1184 ms
scripts.js
992 ms
app-google-play.png
1183 ms
app-app-store.png
1202 ms
like.php
130 ms
vpc6VNjRPXV.js
514 ms
LVx-xkvaJ0b.png
577 ms
vpc6VNjRPXV.js
201 ms
logo.png
167 ms
lang-bg.png
167 ms
fb.png
168 ms
instagram.png
165 ms
loading.gif
169 ms
3_5411627a3894b.jpg
1456 ms
black-tr.png
326 ms
white-tr.png
326 ms
2_5401973d6ca96.jpg
1294 ms
1_53ef06575efe9.jpg
1460 ms
pattern.png
329 ms
we-are-logo.png
486 ms
analytics.js
17 ms
overlay.png
418 ms
2Q-AW1e_taO6pHwMXcXW5w.ttf
11 ms
_aijTyevf54tkVDLy-dlnKCWcynf_cDxXwCLxiixG1c.ttf
33 ms
0ihfXUL2emPh0ROJezvraKCWcynf_cDxXwCLxiixG1c.ttf
34 ms
collect
11 ms
azza.az accessibility score
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
azza.az 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
azza.az 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 Azza.az 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 Azza.az 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.
azza.az
Open Graph description is not detected on the main page of Azza. 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: