5.6 sec in total
771 ms
4.6 sec
220 ms
Visit cleanline.am now to see the best up-to-date Clean Line content for Armenia and also check out these interesting facts you probably never knew about cleanline.am
Քլին Լայն ընկերությունը (CleanLine maqrum) առաջարկում է իր ծառայությունները պրոֆեսիոնալ մաքրման ոլորտում
Visit cleanline.amWe analyzed Cleanline.am page load time and found that the first response time was 771 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cleanline.am performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value12.4 s
0/100
25%
Value8.6 s
17/100
10%
Value910 ms
31/100
30%
Value0.156
74/100
15%
Value12.4 s
15/100
10%
771 ms
1246 ms
45 ms
90 ms
286 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 93% of them (76 requests) were addressed to the original Cleanline.am, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Cleanline.am.
Page size can be reduced by 553.6 kB (18%)
3.0 MB
2.5 MB
In fact, the total size of Cleanline.am main page is 3.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. 60% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 24.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. 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 24.9 kB or 81% of the original size.
Potential reduce by 526.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, Clean Line needs image optimization as it can save up to 526.7 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 260 B
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. Cleanline.am has all CSS files already compressed.
Number of requests can be reduced by 23 (29%)
79
56
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clean Line. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
cleanline.am
771 ms
cleanline.am
1246 ms
fbevents.js
45 ms
gtm.js
90 ms
logo.gif
286 ms
slide-new-11%E2%80%A411%E2%80%A421.jpg
1098 ms
slide-new.jpg
961 ms
1_148_big.jpg
693 ms
1_122_big.jpg
556 ms
1_116_big.jpg
557 ms
1_212_small.jpg
556 ms
1_211_small.jpg
827 ms
1_209_small.jpg
826 ms
1_208_small.jpg
827 ms
1_207_small.jpg
828 ms
1_206_small.jpg
962 ms
1_205_small.jpg
962 ms
1_204_small.jpg
962 ms
1_203_small.jpg
964 ms
1_202_small.jpg
1096 ms
1_201_small.jpg
1097 ms
1_200_small.jpg
1097 ms
1_199_small.jpg
1098 ms
1_198_small.jpg
1237 ms
1_155_small.jpg
1230 ms
1_158_small.jpg
1231 ms
1_90_small.jpg
1232 ms
1_140_small.jpg
1233 ms
1_67_small.jpg
1371 ms
1_139_small.jpg
1366 ms
1_141_small.jpg
1365 ms
1_75_small.jpg
1368 ms
1_77_small.jpg
1368 ms
1_81_small.jpg
1508 ms
1_136_small.jpg
1500 ms
1_70_small.jpg
1501 ms
1_134_small.jpg
1504 ms
1_78_small.jpg
1504 ms
1_135_small.jpg
1505 ms
reset.min.css
1632 ms
style.min.css
1360 ms
button.css
1090 ms
carousel3.css
1091 ms
pager.css
1091 ms
jquery.bxslider.min.css
964 ms
mbextruder.min.css
953 ms
mbex.min.css
954 ms
prettyphoto.css
953 ms
jquery-latest.js
963 ms
script_dropdown.js
824 ms
jquery.hoverintent.min.js
822 ms
jquery.mb.fliptext.js
952 ms
mbextruder.js
953 ms
mbex.min.js
951 ms
jquery.bxslider.min.js
825 ms
order.min.js
823 ms
feed.min.js
851 ms
jcarousellite.js
951 ms
jquery.prettyphoto.js
952 ms
main.min.js
822 ms
1_74_small.jpg
855 ms
slogan.png
852 ms
kita.png
964 ms
111.png
1084 ms
ator.png
962 ms
bnakaran_am.jpg
827 ms
qim_am.jpg
825 ms
patuhan_am.jpg
826 ms
bodyback.gif
678 ms
cleanline.gif
679 ms
phone.png
681 ms
left-animation-clean.gif
682 ms
menububbles.png
805 ms
people.png
815 ms
socialsprite23.png
813 ms
segoeuisl.woff
869 ms
analytics.js
39 ms
hit
540 ms
extruder_blank.png
385 ms
bx_loader.gif
386 ms
collect
12 ms
js
43 ms
cleanline.am accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
[role]s are not contained by their required parent element
[aria-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
cleanline.am 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
Issues were logged in the Issues panel in Chrome Devtools
cleanline.am SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
HY
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cleanline.am can be misinterpreted by Google and other search engines. Our service has detected that Armenian is used on the page, and it does not match the claimed Russian language. Our system also found out that Cleanline.am 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.
cleanline.am
Open Graph description is not detected on the main page of Clean Line. 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: