Tools & Wizards About Us
mayki.kz screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

mayki.kz

Принт на одежду ᐈ Купить одежду с печатью и надписями по актуальной цене в интернет-магазине изделий с принтами на заказ - Алматы, Казахстан, Майки кз

Page Load Speed

12.7 sec in total

First Response

721 ms

Resources Loaded

10.5 sec

Page Rendered

1.4 sec

mayki.kz screenshot

About Website

Welcome to mayki.kz homepage info - get ready to check Mayki best content for Kazakhstan right away, or after learning these important things about mayki.kz

Печать на одежде, футболках и изделиях в Алматы☝Оптом и в розницу по низким ценам в интернет магазине одежды с принтами и рисунками ✅ Доставка по Казахстану ✔️ Детали по номеру

Visit mayki.kz

Key Findings

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

mayki.kz performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

mayki.kz

721 ms

mayki.kz

3763 ms

gtm.js

90 ms

reset.css

242 ms

slick.css

483 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 95% of them (81 requests) were addressed to the original Mayki.kz, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Cdn.rees46.com. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source S2.mayki.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.7 kB (17%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-90%

Potential reduce by 172.9 kB

  • Original 192.5 kB
  • After minification 133.0 kB
  • After compression 19.7 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 59.5 kB, which is 31% 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 172.9 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 47.5 kB

  • Original 1.2 MB
  • After minification 1.1 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. Mayki images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 19.5 kB

  • Original 90.8 kB
  • After minification 90.8 kB
  • After compression 71.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 19.5 kB or 22% of the original size.

CSS Optimization

-29%

Potential reduce by 9.9 kB

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

Requests Breakdown

Number of requests can be reduced by 23 (29%)

Requests Now

80

After Optimization

57

  • Images
  • JavaScript
  • CSS

The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mayki. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

mayki.kz

mayki.kz

721 ms

mayki.kz

mayki.kz

3763 ms

gtm.js

gtm.js

90 ms

reset.css

reset.css

242 ms

slick.css

slick.css

483 ms

slick-theme.css

slick-theme.css

705 ms

style.css

style.css

938 ms

adaptive.css

adaptive.css

725 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

727 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

968 ms

slick.js

slick.js

965 ms

scripts.js

scripts.js

941 ms

cart.js

cart.js

965 ms

app.js

app.js

966 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

1174 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

1173 ms

font-awesome.min.css

font-awesome.min.css

1205 ms

v3.js

v3.js

621 ms

logo.png

logo.png

246 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

4804 ms

whatsapp.svg

whatsapp.svg

242 ms

firm-line-three.png

firm-line-three.png

257 ms

menu.svg

menu.svg

242 ms

search-icon.svg

search-icon.svg

244 ms

phone-icon.svg

phone-icon.svg

235 ms

like-icon.svg

like-icon.svg

404 ms

cart.svg

cart.svg

469 ms

opt_slider.jpg

opt_slider.jpg

1217 ms

slide-3.jpg

slide-3.jpg

1462 ms

3d_constructor.jpg

3d_constructor.jpg

1215 ms

firm-line-sidebar.jpg

firm-line-sidebar.jpg

509 ms

menu-close.svg

menu-close.svg

637 ms

arrow-select.png

arrow-select.png

715 ms

percent.svg

percent.svg

750 ms

product-like.svg

product-like.svg

870 ms

1_4_zoom_sm.png

1_4_zoom_sm.png

968 ms

1_14_zoom_sm.png

1_14_zoom_sm.png

1246 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1354 ms

1_2_zoom_sm.png

1_2_zoom_sm.png

1216 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1477 ms

1_3_zoom_sm.png

1_3_zoom_sm.png

1481 ms

1_2_zoom_sm.png

1_2_zoom_sm.png

1465 ms

1_14_zoom_sm.png

1_14_zoom_sm.png

1500 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1602 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1714 ms

new-product.png

new-product.png

1718 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1729 ms

1_3_zoom_sm.png

1_3_zoom_sm.png

1737 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1757 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1849 ms

1_3_zoom_sm.png

1_3_zoom_sm.png

1971 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1966 ms

1_4_zoom_sm.png

1_4_zoom_sm.png

1984 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1990 ms

watch.js

watch.js

2 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1934 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2154 ms

1_2_zoom_sm.png

1_2_zoom_sm.png

1988 ms

1_3_zoom_sm.png

1_3_zoom_sm.png

1988 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

2012 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

2007 ms

1_14_zoom_sm.png

1_14_zoom_sm.png

2020 ms

1_4_zoom_sm.png

1_4_zoom_sm.png

2071 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

2012 ms

1_3_zoom_sm.png

1_3_zoom_sm.png

1872 ms

1_14_zoom_sm.png

1_14_zoom_sm.png

1817 ms

1_2_zoom_sm.png

1_2_zoom_sm.png

1825 ms

1_2_zoom_sm.png

1_2_zoom_sm.png

1852 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1792 ms

1_2_zoom_sm.png

1_2_zoom_sm.png

1563 ms

1_2_zoom_sm.png

1_2_zoom_sm.png

1572 ms

1_2_zoom_sm.png

1_2_zoom_sm.png

1575 ms

1_2_zoom_sm.png

1_2_zoom_sm.png

1574 ms

1_14_zoom_sm.png

1_14_zoom_sm.png

1614 ms

1_77_zoom_sm.png

1_77_zoom_sm.png

1558 ms

1_1_zoom_sm.png

1_1_zoom_sm.png

1560 ms

rocket.svg

rocket.svg

1546 ms

mail-bg.jpg

mail-bg.jpg

1563 ms

mail-white.svg

mail-white.svg

1553 ms

visa.png

visa.png

1618 ms

mastercard.png

mastercard.png

1550 ms

cloud.png

cloud.png

1558 ms

qiwi.png

qiwi.png

1545 ms

webmoney.png

webmoney.png

1557 ms

yandex.png

yandex.png

1542 ms

Accessibility Review

mayki.kz accessibility score

95

Accessibility Issues

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

Best Practices

mayki.kz best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

mayki.kz SEO score

89

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

mayki.kz

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