7 sec in total
572 ms
5.5 sec
913 ms
Click here to check amazing Cvetochnik content for Kazakhstan. Otherwise, check out these important facts you probably never knew about cvetochnik.kz
Магазин цветов "Цветочник" Алматы, Нур-Султан, Караганда, Семей, Павлодар, Усть-Каменогорск | цветочный магазин, заказать цветы, купить цветы
Visit cvetochnik.kzWe analyzed Cvetochnik.kz page load time and found that the first response time was 572 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
cvetochnik.kz performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value13.5 s
0/100
25%
Value8.6 s
17/100
10%
Value1,330 ms
17/100
30%
Value0.029
100/100
15%
Value21.9 s
1/100
10%
572 ms
1122 ms
189 ms
378 ms
565 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 78% of them (75 requests) were addressed to the original Cvetochnik.kz, 7% (7 requests) were made to B24.cvetochnik.kz and 4% (4 requests) were made to Piper.amocrm.ru. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Cvetochnik.kz.
Page size can be reduced by 765.1 kB (17%)
4.5 MB
3.7 MB
In fact, the total size of Cvetochnik.kz main page is 4.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. 65% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 398.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. 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 398.7 kB or 70% of the original size.
Potential reduce by 199.7 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. Cvetochnik images are well optimized though.
Potential reduce by 123.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 123.1 kB or 13% of the original size.
Potential reduce by 43.7 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. Cvetochnik.kz needs all CSS files to be minified and compressed as it can save up to 43.7 kB or 18% of the original size.
Number of requests can be reduced by 37 (42%)
88
51
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cvetochnik. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
cvetochnik.kz
572 ms
cvetochnik.kz
1122 ms
ui.design-tokens.min.css
189 ms
ui.font.opensans.min.css
378 ms
main.popup.bundle.min.css
565 ms
style.min.css
564 ms
font-awesome.min.css
567 ms
page_9fb62e3d54c83624525052c857030eca_v1.css
566 ms
template_e36008f5b8dca7e29a17ec495628a262_v1.css
754 ms
slick.css
563 ms
slick-theme.css
751 ms
core.min.js
1130 ms
kernel_main_v1.js
945 ms
dexie3.bundle.min.js
943 ms
core_ls.min.js
854 ms
core_frame_cache.min.js
938 ms
protobuf.min.js
944 ms
model.min.js
943 ms
rest.client.min.js
1129 ms
pull.client.min.js
1145 ms
buyoneclick.js
1146 ms
main.popup.bundle.min.js
1323 ms
currency-core.bundle.min.js
1148 ms
core_currency.min.js
1316 ms
basket.js
1316 ms
pixel_identifier.js
854 ms
template_275d894163bf302a31233bf50a776587_v1.js
1327 ms
page_12160fe3a1ef4d608af71e0e7f3f2080_v1.js
1331 ms
slick.min.js
1335 ms
js
61 ms
bundle.js
967 ms
gtm.js
79 ms
close.svg
707 ms
Logotype_header.svg
708 ms
captcha.php
751 ms
facebook-logo.svg
718 ms
Google.svg
720 ms
menu.svg
732 ms
wts.svg
893 ms
search.svg
895 ms
aae513e5396895353055620dce745b09.jpg
1468 ms
favicon.svg
907 ms
60010f6f5107d830595af3fb4c936ebf.png
1294 ms
12896edb1da1028b25fd74225d3c7134.jpeg
1124 ms
231e458316c6519502444f6d42eb74e1.jpg
1453 ms
0c22f7501a2b09a4469253b8e77dd7ca.jpg
1267 ms
da5afe415dff9edd910434c0ec2a74cd.jpg
1281 ms
fdd23e040c0b9e1c17c6450c7e7a422b.jpg
1498 ms
bb239a5260feb84a4e9b055c0165a49a.jpg
1641 ms
37a35cf77382f1a6f94c740422d6f6f3.jpg
1661 ms
00df36aee137d3312801e3aa2fbc4cea.jpg
1427 ms
f279d244a41691238f00082a743d7397.jpeg
1771 ms
form_loader.js
1049 ms
TTNorms-Regular.woff
1517 ms
TTNorms-Medium.woff
1526 ms
554a5644ea3532bce3f2acf1bc25ed48.jpeg
1727 ms
eb9b87b1fe82cf28dcf654fb1c3c4791.jpeg
1871 ms
d7181c586000ca23ebc90fc31a39a962.jpeg
1700 ms
df4f4ff7779d910f1f6ea4274b6b0e6e.jpeg
1499 ms
51ec75a4daa218020485389fea2aba69.jpeg
1512 ms
f0358bc33af08f93b067a2abc84e854e.jpeg
1852 ms
9d0e800de937b07e563e8232e4336485.jpg
1682 ms
65b2f004bb6db5532fb1e6a523c08f8f.jpg
1683 ms
20aaf08e1f4c31c4f9a178b1ece40801.jpg
1571 ms
b75e1a027992928d73c4aac607f0fc91.jpg
1571 ms
watch.js
10 ms
identifier_iframe.html
126 ms
4727ee4d1334b405962c0b6a51b4aa0a.jpg
1675 ms
ba.js
299 ms
init
607 ms
script.js
537 ms
5b3b56a8a97896d2a5170602d5f39a20.jpg
1682 ms
c6045874455813eafb90b14da1e8b2ea.png
2359 ms
loader_2_2spmfb.js
1493 ms
hwp75x5sxsfuo31uiibp.js
513 ms
42938aafb74bccc2aaf6fa4c0c59321d.jpg
1675 ms
pixel_identifier_iframe.js
127 ms
5f35337b3d58ec4d3e1b16c07d7819da.jpg
1541 ms
847055c6bee248836081072d7c2db812.jpg
1681 ms
0aa332f283c165514df0ef4086838a93.jpg
1674 ms
shop.jpg
1688 ms
facebook.svg
1690 ms
instagram.svg
1684 ms
get_cookie
205 ms
bx_stat
180 ms
vk.svg
1683 ms
Visa.svg
1683 ms
MasterCard.svg
1692 ms
ajax.php
218 ms
Amex.svg
1486 ms
Search_Big.svg
1354 ms
loader_6.js
187 ms
polyfill.js
567 ms
call.tracker.js
187 ms
styles.min.css
930 ms
script.min.js
695 ms
cvetochnik.kz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
ARIA IDs are not unique
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
Links do not have a discernible name
cvetochnik.kz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
cvetochnik.kz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cvetochnik.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 Cvetochnik.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.
cvetochnik.kz
Open Graph description is not detected on the main page of Cvetochnik. 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: