Access zags.by. Главный Свадебный Портал Могилёва, Бобруйска, Гомеля, Витебска

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

zags.by

236 ms

zags.by

303 ms

css

80 ms

41 ms

jquery-2.1.3.min.js

74 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 81% of them (95 requests) were addressed to the original Zags.by, 3% (3 requests) were made to I.vimeocdn.com and 2% (2 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Track.soctracker.ru.

Content Size

13.1 MB

After Optimization

12.1 MB

In fact, the total size of Zags.by main page is 13.1 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. 80% 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 12.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 110.2 kB

Original 134.7 kB
After minification 96.3 kB
After compression 24.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 38.3 kB, which is 28% 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 110.2 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 791.1 kB

Original 12.2 MB
After minification 11.4 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. Zags images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 97.0 kB

Original 793.0 kB
After minification 792.8 kB
After compression 696.0 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 97.0 kB or 12% of the original size.

Requests Now

109

After Optimization

The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zags. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 66 to 1 for JavaScripts 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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

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

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

RU
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zags.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Zags.by 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 Zags. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: