CLS.AZ VAHİD MƏRKƏZLƏŞDİRİLMİŞ KİTABXANA PORTALI

  1. Homepage
  2. cls.az

cls.az website information.

cls.az domain name is registered by .AZ top-level domain registry. See the other sites registred in .AZ domain zone.

Following name servers are specified for cls.az domain:

  • ns2.eurosel.az
  • ns1.eurosel.az

According to Alexa traffic rank the highest website cls.az position was 11206 (in the world). The lowest Alexa rank position was 998437. Current position of cls.az in Alexa rank database is below 1 million.

Website cls.az Desktop speed measurement score (41/100) is better than the results of 15.65% of other sites shows that the page desktop performance can be improved.

cls.az Mobile usability score (71/100) is better than the results of 21.61% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of cls.az (34/100) is better than the results of 12.98% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-17-2024 N/AN/A
Nov-16-2024 N/AN/A
Nov-15-2024 N/AN/A
Nov-14-2024 N/AN/A
Nov-13-2024 N/AN/A
Nov-12-2024 N/AN/A
Nov-11-2024 N/AN/A

Advertisement

cls.az Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.


cls.az whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.

cls.az domain is not supported

cls.az server information

Servers Location

IP Address
46.32.171.8
Country
Azerbaijan
Region
Baki
City
Baku

cls.az desktop page speed rank

Last tested: 2019-11-22

Desktop Speed Bad
41/100

cls.az Desktop Speed Test Quick Summary


priority - 83 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 814.2KiB (74% reduction).

Compressing http://cls.az/front/js/jquery-ui.js could save 344.3KiB (75% reduction).
Compressing http://cls.az/front/assets/fdca4542/jquery.js could save 191KiB (70% reduction).
Compressing http://cls.az/front/js/galleria.js could save 100.4KiB (78% reduction).
Compressing http://cls.az/front/js/jquery.js could save 59.8KiB (64% reduction).
Compressing http://cls.az/front/site/libs could save 45.6KiB (80% reduction).
Compressing http://cls.az/front/css/jquery-ui.css could save 26.5KiB (76% reduction).
Compressing http://cls.az/front/css/designlib.css could save 26.3KiB (77% reduction).
Compressing http://cls.az/front/js/mainCarousel.js could save 11.5KiB (73% reduction).
Compressing http://cls.az/front/css/galleria.classic.css could save 3.1KiB (74% reduction).
Compressing http://cls.az/front/js/scripts.js could save 2.2KiB (67% reduction).
Compressing http://cls.az/front/js/galleria.classic.js could save 1.7KiB (64% reduction).
Compressing http://cls.az/front/css/education_map.css could save 1.4KiB (66% reduction).
Compressing http://cls.az/front/js/jquery.mousewheel.min.js could save 576B (50% reduction).

priority - 38 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 370.1KiB (44% reduction).

Minifying http://cls.az/front/js/jquery-ui.js could save 157.9KiB (35% reduction).
Minifying http://cls.az/front/assets/fdca4542/jquery.js could save 128.5KiB (48% reduction).
Minifying http://cls.az/front/js/galleria.js could save 80.5KiB (62% reduction).
Minifying http://cls.az/front/js/scripts.js could save 1.6KiB (48% reduction).
Minifying http://cls.az/front/js/galleria.classic.js could save 1.3KiB (49% reduction).
Minifying http://cls.az/front/js/jquery.mousewheel.min.js could save 420B (36% reduction).

priority - 14 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 8 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://cls.az/front/assets/fdca4542/jquery.js
http://cls.az/front/js/jquery.js
http://cls.az/front/js/scripts.js
http://cls.az/front/js/galleria.js
http://cls.az/front/js/galleria.classic.js
http://cls.az/front/js/jquery.mousewheel.min.js
http://cls.az/front/js/mainCarousel.js
http://cls.az/front/js/jquery-ui.js

Optimize CSS Delivery of the following:

http://cls.az/front/css/education_map.css
http://cls.az/front/css/designlib.css
http://cls.az/front/css/galleria.classic.css
http://cls.az/front/css/jquery-ui.css

priority - 11 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 108KiB (54% reduction).

Compressing http://cls.az/front/images/map_az.png could save 68.1KiB (45% reduction).
Compressing http://cls.az/front/images/box-shadow.png could save 38.3KiB (92% reduction).
Compressing http://cls.az/front/images/ultra.png could save 918B (37% reduction).
Compressing http://cls.az/front/images/arrow2.gif could save 735B (84% reduction).

priority - 9 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://cls.az/front/assets/fdca4542/jquery.js (expiration not specified)
http://cls.az/front/css/designlib.css (expiration not specified)
http://cls.az/front/css/education_map.css (expiration not specified)
http://cls.az/front/css/galleria.classic.css (expiration not specified)
http://cls.az/front/css/jquery-ui.css (expiration not specified)
http://cls.az/front/images/arrow2.gif (expiration not specified)
http://cls.az/front/images/box-shadow.png (expiration not specified)
http://cls.az/front/images/logo.png (expiration not specified)
http://cls.az/front/images/map_az.png (expiration not specified)
http://cls.az/front/images/ultra.png (expiration not specified)
http://cls.az/front/js/galleria.classic.js (expiration not specified)
http://cls.az/front/js/galleria.js (expiration not specified)
http://cls.az/front/js/jquery-ui.js (expiration not specified)
http://cls.az/front/js/jquery.js (expiration not specified)
http://cls.az/front/js/jquery.mousewheel.min.js (expiration not specified)
http://cls.az/front/js/mainCarousel.js (expiration not specified)
http://cls.az/front/js/scripts.js (expiration not specified)
https://www.googletagmanager.com/gtag/js?id=UA-109489792-1 (15 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 2 Reduce server response time

In our test, your server responded in 0.41 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 1 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 14.5KiB (20% reduction).

Minifying http://cls.az/front/css/designlib.css could save 6.2KiB (19% reduction).
Minifying http://cls.az/front/css/jquery-ui.css could save 6KiB (18% reduction).
Minifying http://cls.az/front/css/education_map.css could save 1.5KiB (67% reduction).
Minifying http://cls.az/front/css/galleria.classic.css could save 855B (20% reduction).

cls.az Desktop Resources

Total Resources23
Number of Hosts3
Static Resources19
JavaScript Resources10
CSS Resources4

cls.az Desktop Resource Breakdown

cls.az mobile page speed rank

Last tested: 2017-05-19

Mobile Speed Bad
34/100

cls.az Mobile Speed Test Quick Summary


priority - 83 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 814.3KiB (74% reduction).

Compressing http://cls.az/front/js/jquery-ui.js could save 344.2KiB (75% reduction).
Compressing http://cls.az/front/assets/fdca4542/jquery.js could save 191KiB (70% reduction).
Compressing http://cls.az/front/js/galleria.js could save 100.4KiB (78% reduction).
Compressing http://cls.az/front/js/jquery.js could save 59.7KiB (64% reduction).
Compressing http://cls.az/front/site/libs could save 45.8KiB (80% reduction).
Compressing http://cls.az/front/css/jquery-ui.css could save 26.5KiB (76% reduction).
Compressing http://cls.az/front/css/designlib.css could save 26.3KiB (77% reduction).
Compressing http://cls.az/front/js/mainCarousel.js could save 11.5KiB (73% reduction).
Compressing http://cls.az/front/css/galleria.classic.css could save 3.1KiB (74% reduction).
Compressing http://cls.az/front/js/scripts.js could save 2.2KiB (67% reduction).
Compressing http://cls.az/front/js/galleria.classic.js could save 1.7KiB (64% reduction).
Compressing http://cls.az/front/css/education_map.css could save 1.4KiB (66% reduction).
Compressing http://cls.az/front/js/jquery.mousewheel.min.js could save 576B (50% reduction).

priority - 56 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 8 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://cls.az/front/assets/fdca4542/jquery.js
http://cls.az/front/js/jquery.js
http://cls.az/front/js/scripts.js
http://cls.az/front/js/galleria.js
http://cls.az/front/js/galleria.classic.js
http://cls.az/front/js/jquery.mousewheel.min.js
http://cls.az/front/js/mainCarousel.js
http://cls.az/front/js/jquery-ui.js

Optimize CSS Delivery of the following:

http://cls.az/front/css/education_map.css
http://cls.az/front/css/designlib.css
http://cls.az/front/css/galleria.classic.css
http://cls.az/front/css/jquery-ui.css

priority - 38 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 369.7KiB (44% reduction).

Minifying http://cls.az/front/js/jquery-ui.js could save 157.9KiB (35% reduction).
Minifying http://cls.az/front/assets/fdca4542/jquery.js could save 128.5KiB (48% reduction).
Minifying http://cls.az/front/js/galleria.js could save 80.5KiB (62% reduction).
Minifying http://cls.az/front/js/scripts.js could save 1.6KiB (48% reduction).
Minifying http://cls.az/front/js/galleria.classic.js could save 1.3KiB (49% reduction).

priority - 13 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://cls.az/front/assets/fdca4542/jquery.js (expiration not specified)
http://cls.az/front/css/designlib.css (expiration not specified)
http://cls.az/front/css/education_map.css (expiration not specified)
http://cls.az/front/css/galleria.classic.css (expiration not specified)
http://cls.az/front/css/jquery-ui.css (expiration not specified)
http://cls.az/front/images/arrow2.gif (expiration not specified)
http://cls.az/front/images/box-shadow.png (expiration not specified)
http://cls.az/front/images/logo.png (expiration not specified)
http://cls.az/front/images/map_az.png (expiration not specified)
http://cls.az/front/images/ultra.png (expiration not specified)
http://cls.az/front/js/galleria.classic.js (expiration not specified)
http://cls.az/front/js/galleria.js (expiration not specified)
http://cls.az/front/js/jquery-ui.js (expiration not specified)
http://cls.az/front/js/jquery.js (expiration not specified)
http://cls.az/front/js/jquery.mousewheel.min.js (expiration not specified)
http://cls.az/front/js/mainCarousel.js (expiration not specified)
http://cls.az/front/js/scripts.js (expiration not specified)

priority - 11 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 108KiB (54% reduction).

Compressing http://cls.az/front/images/map_az.png could save 68.1KiB (45% reduction).
Compressing http://cls.az/front/images/box-shadow.png could save 38.3KiB (92% reduction).
Compressing http://cls.az/front/images/ultra.png could save 918B (37% reduction).
Compressing http://cls.az/front/images/arrow2.gif could save 735B (84% reduction).

priority - 2 Reduce server response time

In our test, your server responded in 0.34 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 1 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 14.5KiB (20% reduction).

Minifying http://cls.az/front/css/designlib.css could save 6.2KiB (19% reduction).
Minifying http://cls.az/front/css/jquery-ui.css could save 6KiB (18% reduction).
Minifying http://cls.az/front/css/education_map.css could save 1.5KiB (67% reduction).
Minifying http://cls.az/front/css/galleria.classic.css could save 855B (20% reduction).

cls.az Mobile Resources

Total Resources22
Number of Hosts2
Static Resources17
JavaScript Resources8
CSS Resources4

cls.az Mobile Resource Breakdown

cls.az mobile page usability

Last tested: 2017-05-19

Mobile Usability Medium
71/100

cls.az Mobile Usability Test Quick Summary


priority - 14 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,104 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <p>VAHİD MƏRKƏZLƏŞDİRİLMİŞ</p> falls outside the viewport.
The element <p>KİTABXANA PORTALI</p> falls outside the viewport.
The element <table>Binəqədi MKS…Yasamal MKS</table> falls outside the viewport.
The element <img src="/front/images/ultra.png"> falls outside the viewport.

priority - 10 Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

priority - 9 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://binagadi.cls.az">Binəqədi MKS</a> and 10 others are close to other tap targets.

priority - 8 Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

VAHİD MƏRKƏZLƏŞDİRİLMİŞ and 1 others render only 5 pixels tall (13 CSS pixels).

Binəqədi MKS and 10 others render only 5 pixels tall (13 CSS pixels).

Bütün hüquqlar qorunur. and 1 others render only 5 pixels tall (12 CSS pixels).

Azərbaycan Res…izm Nazirliyi. renders only 5 pixels tall (12 CSS pixels).

cls.az similar domains

Similar domains:
www.cls.com
www.cls.net
www.cls.org
www.cls.info
www.cls.biz
www.cls.us
www.cls.mobi
www.ls.az
www.cls.az
www.xls.az
www.cxls.az
www.xcls.az
www.dls.az
www.cdls.az
www.dcls.az
www.fls.az
www.cfls.az
www.fcls.az
www.vls.az
www.cvls.az
www.vcls.az
www.cs.az
www.cps.az
www.clps.az
www.cpls.az
www.cos.az
www.clos.az
www.cols.az
www.cks.az
www.clks.az
www.ckls.az
www.cl.az
www.clw.az
www.clsw.az
www.clws.az
www.cle.az
www.clse.az
www.cles.az
www.cld.az
www.clsd.az
www.clds.az
www.clz.az
www.clsz.az
www.clzs.az
www.clx.az
www.clsx.az
www.clxs.az
www.cla.az
www.clsa.az
www.clas.az

cls.az Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.

cls.az TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.