Access zub.am. ZUB.AM Հայաստանի ատամնաբուժարաններ | ստոմատոլոգիական ծառայություններ | ատամնաբույժ | ստոմատոլոգիական...

zub.am screenshot

25

Performance

Renders faster than
44% of other websites
77

Accessibility

Visual factors better than
that of 44% of websites
67

Best Practices

More advanced features
available than in
24% of websites
58

SEO

Google-friendlier than
21% of websites

First Response

472 ms

Resources Loaded

4.4 sec

Page Rendered

183 ms

zub.am screenshot

About Website

Visit zub.am now to see the best up-to-date ZUB content for Armenia and also check out these interesting facts you probably never knew about zub.am

Հայաստանի ատամնաբուժարաններ – գտնել ատամնաբուժարան, zub.am, ստոմատոլոգիական ծառայություններ, ատամնաբույժ, ստոմատոլոգիական կլինիկա, 32 ատամ atam, atamnabuj, atamnabujaranner

Visit zub.am

Key Findings

We analyzed Zub.am page load time and found that the first response time was 472 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

zub.am

472 ms

zub.am

742 ms

main.css

134 ms

style.css

269 ms

header.css

356 ms

Our browser made a total of 153 requests to load all elements on the main page. We found that 74% of them (113 requests) were addressed to the original Zub.am, 9% (14 requests) were made to Manager.am and 8% (13 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Zub.am.

Content Size

1.3 MB

After Optimization

1.1 MB

In fact, the total size of Zub.am main page is 1.3 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. 65% of websites need less resources to load. Javascripts take 580.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 106.6 kB

Original 125.1 kB
After minification 110.2 kB
After compression 18.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. This page needs HTML code to be minified as it can gain 14.9 kB, which is 12% 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 106.6 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 25.7 kB

Original 552.3 kB
After minification 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. ZUB images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 12.0 kB

Original 580.6 kB
After minification 580.6 kB
After compression 568.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.

CSS Optimization

-20%

Potential reduce by 6.5 kB

Original 32.0 kB
After minification 32.0 kB
After compression 25.5 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. Zub.am needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 20% of the original size.

Requests Now

150

After Optimization

102

The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ZUB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

Low

No form fields have multiple labels

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Language and Encoding

Language Detected

HY
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zub.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 English language. Our system also found out that Zub.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.

Social Sharing Optimization

zub.am

Open Graph description is not detected on the main page of ZUB. 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: