Tools & Wizards About Us
aizorel.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 0

    Best Practices

  • 83

    SEO

    Google-friendlier than
    46% of websites

aizorel.com

Бюро путешествий «Айзорэль»

Page Load Speed

3.7 sec in total

First Response

488 ms

Resources Loaded

3 sec

Page Rendered

224 ms

aizorel.com screenshot

About Website

Welcome to aizorel.com homepage info - get ready to check Aizorel best content for Russia right away, or after learning these important things about aizorel.com

Лучшие детские лагеря в Европе и в России, обучение детей за рубежом! Экскурсии и отдых в Европе, России и странах СНГ.

Visit aizorel.com

Key Findings

We analyzed Aizorel.com page load time and found that the first response time was 488 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

aizorel.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.039

100/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

aizorel.com

488 ms

www.aizorel.com

689 ms

styles.reset.css

166 ms

styles.global.css

330 ms

jquery.js

249 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 60% of them (18 requests) were addressed to the original Aizorel.com, 13% (4 requests) were made to Google-analytics.com and 10% (3 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cs15.livetex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 150.4 kB (29%)

Content Size

518.7 kB

After Optimization

368.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aizorel.com main page is 518.7 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. 15% of websites need less resources to load. Images take 357.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 33.7 kB

  • Original 43.9 kB
  • After minification 40.3 kB
  • After compression 10.2 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 33.7 kB or 77% of the original size.

Image Optimization

-14%

Potential reduce by 50.0 kB

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

JavaScript Optimization

-53%

Potential reduce by 51.8 kB

  • Original 97.5 kB
  • After minification 89.6 kB
  • After compression 45.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 51.8 kB or 53% of the original size.

CSS Optimization

-77%

Potential reduce by 15.0 kB

  • Original 19.5 kB
  • After minification 13.5 kB
  • After compression 4.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. Aizorel.com needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (69%)

Requests Now

26

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aizorel.com

aizorel.com

488 ms

www.aizorel.com

www.aizorel.com

689 ms

styles.reset.css

styles.reset.css

166 ms

styles.global.css

styles.global.css

330 ms

jquery.js

jquery.js

249 ms

colorbox.css

colorbox.css

350 ms

jquery.colorbox.min.js

jquery.colorbox.min.js

491 ms

actions.global.js

actions.global.js

350 ms

superfish.css

superfish.css

350 ms

hoverIntent.js

hoverIntent.js

351 ms

superfish.js

superfish.js

492 ms

jquery.treeview.js

jquery.treeview.js

493 ms

jquery.treeview.css

jquery.treeview.css

493 ms

analytics.js

analytics.js

112 ms

logo

logo

345 ms

home.gif

home.gif

203 ms

logo.gif

logo.gif

194 ms

UNI_zel.jpg

UNI_zel.jpg

1103 ms

fire128.png

fire128.png

320 ms

univer.png

univer.png

450 ms

horn128.png

horn128.png

330 ms

usd_cb_8831.gif

usd_cb_8831.gif

348 ms

dm_cb88x31.gif

dm_cb88x31.gif

497 ms

hit

hit

575 ms

watch.js

watch.js

4 ms

ga.js

ga.js

207 ms

client.js

client.js

1263 ms

collect

collect

89 ms

__utm.gif

__utm.gif

27 ms

hit

hit

135 ms

Accessibility Review

aizorel.com accessibility score

71

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

Image elements do not have [alt] attributes

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.

SEO Factors

aizorel.com SEO score

83

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aizorel.com 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 Aizorel.com 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

aizorel.com

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