Tools & Wizards About Us
atto.uz screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

atto.uz

Купить транспортную карту atto в Ташкенте | ATTO.UZ

Page Load Speed

9.6 sec in total

First Response

793 ms

Resources Loaded

8.6 sec

Page Rendered

162 ms

atto.uz screenshot

About Website

Visit atto.uz now to see the best up-to-date ATTO content and also check out these interesting facts you probably never knew about atto.uz

Регестрируйтесь и оплачивайте проезд в Ташкенте используя единую транспортную карту с бесконтактной техногией NFC, купить проездную карту можно в кассах метрополитена и в точках продаж проездных билет...

Visit atto.uz

Key Findings

We analyzed Atto.uz page load time and found that the first response time was 793 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

atto.uz performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.207

60/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

atto.uz

793 ms

uz

2689 ms

fonts.css

482 ms

font-awesome.min.css

727 ms

JXD8xkuBXlWC4fEnRaeNQSyRwmxUG65hVXNewqmd.png

2221 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 95% of them (18 requests) were addressed to the original Atto.uz, 5% (1 request) were made to Webadminapi.atto.uz. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Atto.uz.

Page Optimization Overview & Recommendations

Page size can be reduced by 448.2 kB (63%)

Content Size

710.2 kB

After Optimization

262.0 kB

  • HTML
  • Images

In fact, the total size of Atto.uz main page is 710.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 468.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 389.7 kB

  • Original 468.1 kB
  • After minification 466.0 kB
  • After compression 78.4 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 389.7 kB or 83% of the original size.

Image Optimization

-24%

Potential reduce by 58.5 kB

  • Original 242.1 kB
  • After minification 183.6 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, ATTO needs image optimization as it can save up to 58.5 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 5 (36%)

Requests Now

14

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

atto.uz

atto.uz

793 ms

uz

uz

2689 ms

fonts.css

fonts.css

482 ms

font-awesome.min.css

font-awesome.min.css

727 ms

JXD8xkuBXlWC4fEnRaeNQSyRwmxUG65hVXNewqmd.png

JXD8xkuBXlWC4fEnRaeNQSyRwmxUG65hVXNewqmd.png

2221 ms

logo.877ef28.svg

logo.877ef28.svg

486 ms

appstore.53994a2.svg

appstore.53994a2.svg

486 ms

googleplay.e7420e2.svg

googleplay.e7420e2.svg

722 ms

banner-background.fbf4fa0.svg

banner-background.fbf4fa0.svg

720 ms

logo-white.bd099b3.svg

logo-white.bd099b3.svg

723 ms

b3be321.js

b3be321.js

774 ms

6154993.js

6154993.js

776 ms

81b9210.js

81b9210.js

1005 ms

5ede275.js

5ede275.js

1203 ms

d940c91.js

d940c91.js

1927 ms

5c77606.js

5c77606.js

1212 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1002 ms

SFProDisplay-Bold.ttf

SFProDisplay-Bold.ttf

1461 ms

Gilroy-Bold.ttf

Gilroy-Bold.ttf

736 ms

Accessibility Review

atto.uz accessibility score

66

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

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

Impact

Issue

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

atto.uz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

atto.uz SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Atto.uz can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Atto.uz 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

atto.uz

Open Graph data is detected on the main page of ATTO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: