Tools & Wizards About Us
atto.uz screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

atto.uz

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

Page Load Speed

13.8 sec in total

First Response

708 ms

Resources Loaded

12.9 sec

Page Rendered

196 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 708 ms and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

atto.uz performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value23.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,540 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.168

70/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

atto.uz

708 ms

uz

7015 ms

fonts.css

359 ms

font-awesome.min.css

541 ms

JXD8xkuBXlWC4fEnRaeNQSyRwmxUG65hVXNewqmd.png

1805 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 (7 sec) belongs to the original domain Atto.uz.

Page Optimization Overview & Recommendations

Page size can be reduced by 510.7 kB (66%)

Content Size

778.2 kB

After Optimization

267.5 kB

  • HTML
  • Images

In fact, the total size of Atto.uz main page is 778.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. 20% of websites need less resources to load. HTML takes 536.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 452.1 kB

  • Original 536.0 kB
  • After minification 534.0 kB
  • After compression 83.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 452.1 kB or 84% 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

708 ms

uz

uz

7015 ms

fonts.css

fonts.css

359 ms

font-awesome.min.css

font-awesome.min.css

541 ms

JXD8xkuBXlWC4fEnRaeNQSyRwmxUG65hVXNewqmd.png

JXD8xkuBXlWC4fEnRaeNQSyRwmxUG65hVXNewqmd.png

1805 ms

logo.svg

logo.svg

340 ms

appstore.svg

appstore.svg

391 ms

googleplay.svg

googleplay.svg

520 ms

banner-background.svg

banner-background.svg

522 ms

logo-white.svg

logo-white.svg

523 ms

runtime.js

runtime.js

579 ms

index.js

index.js

584 ms

index.js

index.js

1317 ms

app.js

app.js

1777 ms

app.js

app.js

2560 ms

app.js

app.js

1344 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

964 ms

SFProDisplay-Bold.ttf

SFProDisplay-Bold.ttf

952 ms

Gilroy-Bold.ttf

Gilroy-Bold.ttf

1131 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

92

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

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

    EN

  • 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 English 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: