Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

hottour.kz

Горящие туры и путёвки в 2024 вылет из Алматы, Астаны, Казахстана от HOT TOUR / ХОТ ТУР - надёжное Турагентство и Туроператоры, наш официальный сайт h...

Page Load Speed

14.3 sec in total

First Response

650 ms

Resources Loaded

12.8 sec

Page Rendered

821 ms

hottour.kz screenshot

About Website

Click here to check amazing HOT TOUR content for Kazakhstan. Otherwise, check out these important facts you probably never knew about hottour.kz

Горящие туры от HOT TOUR (ХОТ ТУР) - в 2024 предлагает горящие туры и горячие путёвки из Алматы, Астаны, Актобе, Шымкента, Атырау, Актау и Казахстана. Дешевые и низкие цены на туры из Алматы, Астаны, ...

Visit hottour.kz

Key Findings

We analyzed Hottour.kz page load time and found that the first response time was 650 ms and then it took 13.6 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

hottour.kz performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value26.9 s

0/100

10%

TBT (Total Blocking Time)

Value13,800 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value53.0 s

0/100

10%

Network Requests Diagram

hottour.kz

650 ms

hottour.kz

2732 ms

owl.carousel.css

511 ms

owl.axeld.css

512 ms

owl.carousel.css

511 ms

Our browser made a total of 210 requests to load all elements on the main page. We found that 90% of them (189 requests) were addressed to the original Hottour.kz, 2% (4 requests) were made to Travelpayouts.com and 1% (3 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Hottour.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (30%)

Content Size

3.8 MB

After Optimization

2.7 MB

In fact, the total size of Hottour.kz main page is 3.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 318.3 kB

  • Original 446.8 kB
  • After minification 367.6 kB
  • After compression 128.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 79.2 kB, which is 18% 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 318.3 kB or 71% of the original size.

Image Optimization

-7%

Potential reduce by 142.8 kB

  • Original 1.9 MB
  • After minification 1.8 MB

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. HOT TOUR images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 646.7 kB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 684.3 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 646.7 kB or 49% of the original size.

CSS Optimization

-29%

Potential reduce by 31.5 kB

  • Original 107.8 kB
  • After minification 107.7 kB
  • After compression 76.3 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. Hottour.kz needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 105 (52%)

Requests Now

203

After Optimization

98

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

Accessibility Review

hottour.kz accessibility score

68

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

hottour.kz best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

hottour.kz SEO score

78

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hottour.kz can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Hottour.kz 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

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