7.1 sec in total
477 ms
4 sec
2.6 sec
Click here to check amazing Carte content for Belarus. Otherwise, check out these important facts you probably never knew about carte.by
Заказывай еду и бронируй столики, оставляй отзывы и участвуй в рейтингах, получай баллы и меняй их на сувениры.
Visit carte.byWe analyzed Carte.by page load time and found that the first response time was 477 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
carte.by performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value12.3 s
0/100
25%
Value11.1 s
6/100
10%
Value1,260 ms
19/100
30%
Value0.001
100/100
15%
Value12.5 s
14/100
10%
477 ms
916 ms
589 ms
359 ms
368 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 88% of them (46 requests) were addressed to the original Carte.by, 6% (3 requests) were made to and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cdn.carte.by.
Page size can be reduced by 540.8 kB (24%)
2.2 MB
1.7 MB
In fact, the total size of Carte.by main page is 2.2 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. 35% of websites need less resources to load. Images take 758.5 kB which makes up the majority of the site volume.
Potential reduce by 416.3 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 173.5 kB, which is 38% 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 416.3 kB or 92% of the original size.
Potential reduce by 15.3 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. Carte images are well optimized though.
Potential reduce by 85.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 85.7 kB or 26% of the original size.
Potential reduce by 23.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. Carte.by has all CSS files already compressed.
Number of requests can be reduced by 37 (88%)
42
5
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carte. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
carte.by
477 ms
carte.by
916 ms
asset_7b0f400501930db3c26c5666d9ce9a42.css
589 ms
asset_1289336d1b00fcd6f1c911a70cf198c8.css
359 ms
asset_77a02103379b9ae0f84818b3c8059459.css
368 ms
asset_33aec7ba7181399d46f70485a48be9c1.css
375 ms
asset_16800c5f7d40d0c866dda6f40413c304.css
376 ms
asset_921cbda44ac149871218a86ebf1747c7.css
641 ms
asset_c93b5677c6a4ee579cda640224f2d09f.css
477 ms
asset_2b097ee17d9e5274231694e7c3c41f0b.css
494 ms
asset_e9dd40cf53abce3403f645915d91c506.css
498 ms
asset_0e4b5fa665f90c655c9744cee35cb4c7.css
500 ms
asset_ca2f0ee27b44801040cf39b35a75e776.css
595 ms
asset_dd524b4dd26ec19eae9a1e09bc659f19.css
618 ms
asset_f5cf1d7c757a729deb2d385c9b3e3c82.css
621 ms
asset_1cecd3abfac4392505bf1062c87367d7.css
625 ms
asset_7b655c0b6fe536ae6ad591bec0106f35.css
706 ms
asset_0463a3ea56cb4fdd99bdab9f65dd3fc3.css
713 ms
asset_fbe50cf761c51db6b6db19fc564fc083.css
741 ms
asset_ee5c4279b4fd9f47cd3782f88585e21f.css
745 ms
asset_641d1b55f36ebce606599d97459bf13d.css
748 ms
asset_9dacbc051ba9e5e14aca55470714146d.css
1284 ms
,
1 ms
logo-carte.svg
701 ms
,
9 ms
,
5 ms
js
61 ms
asset_438a57a46c0ba6f422b5464efc8562fa.js
587 ms
asset_065f7458fb250fee2780c6a518b71f51.js
620 ms
asset_093aae6d28d72efdb8a33f0dd24db886.js
623 ms
asset_fe8307ed4ee4eafc31c477207fc45a89.js
876 ms
asset_b81b9a8fbd84a17409f04d8df4e390b7.js
694 ms
asset_933d701eb3f3f1f76f3dd442d87d2ae5.js
823 ms
asset_8d60198bdd2b6dfc58bd98c3d2ad8a4c.js
744 ms
asset_cf2b7a4fe7ef9086d38188947f6a2f11.js
748 ms
asset_4cda72b3e764120e23d5aca483f90706.js
812 ms
asset_ad3d19a311551e25cee85862ac77807d.js
867 ms
asset_8b4f3e5f919acb032cba03acb0ba2da0.js
873 ms
asset_cb638ff324f88f6747cb75264f4be899.js
930 ms
asset_18d7914300db21a2f48d84478d62b445.js
942 ms
asset_468dc11ab61d7cf00d9c3778b38d189c.js
990 ms
asset_6339506fd7a25465542d362ade65899d.js
996 ms
asset_d82bf3c5877a5a51220f1886d8057937.js
890 ms
asset_c4e159c8c084d4da651c1b7426046168.js
1066 ms
logo-carte.svg
1061 ms
a6275-9190e6c80cd158c22683c3578152c829---png_2000x240_95bc8_convert.png
1536 ms
gtm.js
101 ms
SFProDisplay-Regular.woff
380 ms
SFProDisplay-Medium.woff
628 ms
SFProDisplay-Semibold.woff
506 ms
SFProDisplay-Bold.woff
378 ms
SFProDisplay-Heavy.woff
354 ms
carte.by accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
carte.by best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
carte.by SEO score
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 Carte.by 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 Carte.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.
carte.by
Open Graph description is not detected on the main page of Carte. 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: