4 sec in total
405 ms
2.8 sec
759 ms
Welcome to run.az homepage info - get ready to check RUN best content for Azerbaijan right away, or after learning these important things about run.az
Azəri mahnılar, Dance, Dini mahnılar, Eurovision 2018, Fars mahnılar, Film və Serial, Meyxanalar, Music for your sports, Oyun havaları, Qarışıq, Rus mahnıları, Trance, Türk mahnıları, Xarici mahnılar,...
Visit run.azWe analyzed Run.az page load time and found that the first response time was 405 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
run.az performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.3 s
42/100
25%
Value7.4 s
28/100
10%
Value1,240 ms
19/100
30%
Value0.003
100/100
15%
Value13.1 s
12/100
10%
405 ms
473 ms
499 ms
119 ms
357 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Run.az, 76% (41 requests) were made to Mp3.run.az and 4% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (859 ms) relates to the external source Mp3.run.az.
Page size can be reduced by 206.4 kB (15%)
1.4 MB
1.2 MB
In fact, the total size of Run.az main page is 1.4 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 816.6 kB which makes up the majority of the site volume.
Potential reduce by 49.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 49.5 kB or 81% of the original size.
Potential reduce by 29.4 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. RUN images are well optimized though.
Potential reduce by 125.2 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 125.2 kB or 27% of the original size.
Potential reduce by 2.2 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. Run.az has all CSS files already compressed.
Number of requests can be reduced by 10 (21%)
48
38
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RUN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
run.az
405 ms
mp3.run.az
473 ms
mp3.run.az
499 ms
default.css
119 ms
jquery.js
357 ms
jqueryui.js
429 ms
dle_js.js
310 ms
styles.css
306 ms
engine.css
472 ms
adsbygoogle.js
193 ms
js
60 ms
counter2.0.js
661 ms
libs.js
354 ms
show_ads_impl.js
462 ms
js
58 ms
analytics.js
95 ms
logo.png
153 ms
1711378230_sddefault.jpg
270 ms
1711378173_maxresdefault.jpg
182 ms
1711378083_hqdefault.jpg
238 ms
1711378070_maxresdefault-2.jpg
135 ms
1711377946_maxresdefault-1.jpg
238 ms
1711265616_sddefault-3.jpg
238 ms
1711265499_sddefault-4.jpg
270 ms
1711265476_maxresdefault-4.jpg
271 ms
1711265396_maxresdefault-6.jpg
340 ms
1711265319_maxresdefault-2.jpg
340 ms
1711265277_sddefault-2.jpg
340 ms
1711265183_maxresdefault.jpg
393 ms
1711265188_sddefault.jpg
394 ms
1711265057_maxresdefault-7.jpg
394 ms
1711264982_maxresdefault-3.jpg
441 ms
1711264997_maxresdefault-1.jpg
441 ms
1711264879_maxresdefault-5.jpg
443 ms
1711264783_sddefault-1.jpg
505 ms
1711264784_hqdefault-1.jpg
506 ms
1711264665_hqdefault.jpg
508 ms
1710532625_maxresdefault.jpg
543 ms
1710328372_maxresdefault-2.jpg
543 ms
no_image.jpg
544 ms
1707231740_maxresdefault-47.jpg
657 ms
1707036098_maxresdefault-37.jpg
655 ms
1707035950_maxresdefault-35.jpg
656 ms
1707035913_sddefault-5.jpg
657 ms
1707035827_maxresdefault-36.jpg
656 ms
aci.js
660 ms
GothamProRegular.woff
623 ms
GothamProBold.woff
725 ms
fontawesome-webfont.woff
859 ms
collect
12 ms
counter.php
143 ms
hit
490 ms
zrt_lookup.html
38 ms
ads
86 ms
run.az 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.
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
Links do not have a discernible name
run.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
run.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
AZ
AZ
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Run.az can be misinterpreted by Google and other search engines. Our service has detected that Azerbaijani is used on the page, and it matches the claimed language. Our system also found out that Run.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.
run.az
Open Graph description is not detected on the main page of RUN. 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: