Tools & Wizards About Us
esquire.kz screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

esquire.kz

Esquire Kazakhstan - электронный журнал для умных мужчин

Page Load Speed

24.2 sec in total

First Response

421 ms

Resources Loaded

22.8 sec

Page Rendered

957 ms

esquire.kz screenshot

About Website

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

Официальный сайт журнала Esquire Kazakhstan - life style современного, умного, образованного мужчины, разбирающегося в науке, моде и литературе.

Visit esquire.kz

Key Findings

We analyzed Esquire.kz page load time and found that the first response time was 421 ms and then it took 23.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

esquire.kz performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value18.8 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,660 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.172

69/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

esquire.kz

421 ms

esquire.kz

815 ms

css2

35 ms

js

70 ms

style.min.css

165 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 66% of them (67 requests) were addressed to the original Esquire.kz, 9% (9 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Goodhouse.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 134.9 kB (6%)

Content Size

2.3 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Esquire.kz main page is 2.3 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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 132.3 kB

  • Original 162.2 kB
  • After minification 147.7 kB
  • After compression 29.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 132.3 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 617 B

  • Original 1.9 MB
  • After minification 1.9 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. Esquire images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.9 kB

  • Original 207.0 kB
  • After minification 207.0 kB
  • After compression 205.1 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 62 (71%)

Requests Now

87

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

esquire.kz

esquire.kz

421 ms

esquire.kz

esquire.kz

815 ms

css2

css2

35 ms

js

js

70 ms

style.min.css

style.min.css

165 ms

app.min.css

app.min.css

328 ms

style.css

style.css

476 ms

motion-ui.min.css

motion-ui.min.css

477 ms

slick.css

slick.css

476 ms

slick-theme.css

slick-theme.css

482 ms

flaticon.css

flaticon.css

483 ms

animate.min.css

animate.min.css

489 ms

cssET.css

cssET.css

637 ms

adfox.css

adfox.css

634 ms

style2.css

style2.css

635 ms

jquery.min.js

jquery.min.js

806 ms

jquery-migrate.min.js

jquery-migrate.min.js

647 ms

loadmoreFrontPage.js

loadmoreFrontPage.js

649 ms

foundation.core.min.js

foundation.core.min.js

794 ms

slick.min.js

slick.min.js

794 ms

js.cookie.js

js.cookie.js

795 ms

js.et.js

js.et.js

809 ms

app.js

app.js

809 ms

dd1f55e4c3f389f73ab632f6da823228_1.js

dd1f55e4c3f389f73ab632f6da823228_1.js

157 ms

loadmore.js

loadmore.js

953 ms

css-lazy-load.min.js

css-lazy-load.min.js

953 ms

adsbygoogle.js

adsbygoogle.js

119 ms

es5-shims.min.js

es5-shims.min.js

551 ms

share.js

share.js

791 ms

motion-ui.min.js

motion-ui.min.js

952 ms

foundation.util.mediaQuery.min.js

foundation.util.mediaQuery.min.js

964 ms

foundation.interchange.min.js

foundation.interchange.min.js

967 ms

foundation.util.keyboard.min.js

foundation.util.keyboard.min.js

965 ms

foundation.util.triggers.min.js

foundation.util.triggers.min.js

1110 ms

foundation.offcanvas.min.js

foundation.offcanvas.min.js

1110 ms

foundation.util.motion.min.js

foundation.util.motion.min.js

1111 ms

foundation.responsiveToggle.min.js

foundation.responsiveToggle.min.js

1126 ms

foundation.sticky.min.js

foundation.sticky.min.js

1125 ms

foundation.util.touch.min.js

foundation.util.touch.min.js

1128 ms

foundation.util.box.min.js

foundation.util.box.min.js

1270 ms

foundation.reveal.min.js

foundation.reveal.min.js

1269 ms

foundation.dropdown.min.js

foundation.dropdown.min.js

1269 ms

foundation.util.nest.min.js

foundation.util.nest.min.js

1286 ms

foundation.accordionMenu.min.js

foundation.accordionMenu.min.js

1287 ms

js.gallery-post.js

js.gallery-post.js

1134 ms

lazyload.min.js

lazyload.min.js

1119 ms

context.js

context.js

946 ms

header-bidding.js

header-bidding.js

1065 ms

gtm.js

gtm.js

106 ms

tag.js

tag.js

910 ms

fw24-preco_16x9_12-355x180.png

fw24-preco_16x9_12-355x180.png

355 ms

mycollages-2-355x180.jpg

mycollages-2-355x180.jpg

202 ms

dsc06550-355x180.jpg

dsc06550-355x180.jpg

201 ms

maxb-1_resized-1-355x180.jpg

maxb-1_resized-1-355x180.jpg

200 ms

variant-oblozhki-3-355x180.jpg

variant-oblozhki-3-355x180.jpg

200 ms

pizduk1.png

pizduk1.png

252 ms

logo.png

logo.png

354 ms

p1.png

p1.png

354 ms

p6-1-2.png

p6-1-2.png

354 ms

p3.png

p3.png

354 ms

telegram-32.png

telegram-32.png

384 ms

KFOmCnqEu92Fr1Me5mZNCzc.woff

KFOmCnqEu92Fr1Me5mZNCzc.woff

88 ms

KFOlCnqEu92Fr1MmEU9vAB0_IsE.woff

KFOlCnqEu92Fr1MmEU9vAB0_IsE.woff

118 ms

KFOlCnqEu92Fr1MmSU5vAB0_IsE.woff

KFOlCnqEu92Fr1MmSU5vAB0_IsE.woff

117 ms

KFOkCnqEu92Fr1MmgWxMKTU1Kg.woff

KFOkCnqEu92Fr1MmgWxMKTU1Kg.woff

118 ms

KFOlCnqEu92Fr1MmWUlvAB0_IsE.woff

KFOlCnqEu92Fr1MmWUlvAB0_IsE.woff

118 ms

sdk.js

sdk.js

86 ms

code.js

code.js

742 ms

KFOkCnqEu92Fr1Mu52xMKTU1Kg.woff

KFOkCnqEu92Fr1Mu52xMKTU1Kg.woff

105 ms

zYXgKVElMYYaJe8bpLHnCwDKtdXUEo5M.woff

zYXgKVElMYYaJe8bpLHnCwDKtdXUEo5M.woff

154 ms

zYX9KVElMYYaJe8bpLHnCwDKjSL9MIVmc9_r.woff

zYX9KVElMYYaJe8bpLHnCwDKjSL9MIVmc9_r.woff

105 ms

zYX9KVElMYYaJe8bpLHnCwDKjXr8MIVmc9_r.woff

zYX9KVElMYYaJe8bpLHnCwDKjXr8MIVmc9_r.woff

257 ms

banner-vhodnaja.jpg

banner-vhodnaja.jpg

864 ms

mycollages-1-1.jpeg

mycollages-1-1.jpeg

707 ms

whatsapp-image-2024-05-28-at-16.50.09.jpeg

whatsapp-image-2024-05-28-at-16.50.09.jpeg

1023 ms

img_6151.jpg

img_6151.jpg

1207 ms

slickarrow.png

slickarrow.png

415 ms

eski-1.png

eski-1.png

434 ms

pizduk.png

pizduk.png

575 ms

ddddxxxeeeepspspdddjjdjdj.webp

ddddxxxeeeepspspdddjjdjdj.webp

893 ms

356960964_225846070327704_6683469243417017630_n.jpg

356960964_225846070327704_6683469243417017630_n.jpg

1046 ms

ilon-mask.jpg

ilon-mask.jpg

854 ms

mntgr2.jpeg

mntgr2.jpeg

1015 ms

181.png

181.png

19925 ms

Flaticon.svg

Flaticon.svg

959 ms

Flaticon.woff

Flaticon.woff

993 ms

sdk.js

sdk.js

52 ms

40 ms

sync-loader.js

sync-loader.js

741 ms

counter

counter

121 ms

dyn-goal-config.js

dyn-goal-config.js

248 ms

advert.gif

advert.gif

656 ms

fontawesome-all.css

fontawesome-all.css

164 ms

fa-solid-900.woff

fa-solid-900.woff

174 ms

fa-regular-400.woff

fa-regular-400.woff

160 ms

sync_cookie_image_decide

sync_cookie_image_decide

144 ms

sync_cookie_image_decide

sync_cookie_image_decide

140 ms

1

1

135 ms

44816287

44816287

205 ms

1

1

260 ms

1

1

267 ms

tracker

tracker

122 ms

Accessibility Review

esquire.kz accessibility score

88

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-*] attributes do not match their roles

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.

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

Links do not have a discernible name

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

Best Practices

esquire.kz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

esquire.kz SEO score

91

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

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 Esquire.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 Esquire.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

esquire.kz

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