9.7 sec in total
493 ms
5.5 sec
3.7 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 493 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
carte.by performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value9.6 s
0/100
25%
Value7.3 s
29/100
10%
Value220 ms
87/100
30%
Value0.001
100/100
15%
Value6.9 s
53/100
10%
493 ms
1028 ms
474 ms
338 ms
340 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 70% of them (40 requests) were addressed to the original Carte.by, 14% (8 requests) were made to Cdn.carte.by and 4% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Cdn.carte.by.
Page size can be reduced by 501.2 kB (17%)
3.0 MB
2.5 MB
In fact, the total size of Carte.by main page is 3.0 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. 50% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 189.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 71.9 kB, which is 35% 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 189.7 kB or 92% of the original size.
Potential reduce by 270.8 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 3.9 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.
Potential reduce by 36.8 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 needs all CSS files to be minified and compressed as it can save up to 36.8 kB or 20% of the original size.
Number of requests can be reduced by 29 (62%)
47
18
The browser has sent 47 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 15 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
carte.by
493 ms
carte.by
1028 ms
asset_1474fe610f116b8d092c21d4f1b26374.css
474 ms
asset_aa84ad3d79b045fb6e456911cf843ae9.css
338 ms
asset_5814b81c27efc2a60129f16c73de1c16.css
340 ms
asset_dc9342d8cef580528f9f866966e8eee4.css
342 ms
asset_fefda0d6be355eb8adc1ea2ae23081e7.css
346 ms
asset_f44ec98d89d347d0805d5f52269b4e4a.css
367 ms
asset_d6b565e24031ced67fcfc15191358a79.css
446 ms
asset_3fa82bc9383ac5510817ee1aab5db8a5.css
450 ms
asset_4edd303370317299f874e0b264ac1f8e.css
447 ms
asset_8a276040280f44bf10e6681686ade801.css
460 ms
asset_c1ab81ee6dfe7d05a0eda4ec783a821f.css
486 ms
asset_f67b4eaf501b6404d0f8160d8f375127.css
557 ms
asset_14e6d8714072413c4cb7d21e5ee530cf.css
558 ms
asset_f7d28e103bbb1de628a55941cb2cf59f.css
559 ms
asset_2c492ec1802a96ca02bfcb35963c285c.css
572 ms
asset_2eebe0dc2c2c68418b13dc57908249b3.css
591 ms
,
3 ms
logo-carte.svg
977 ms
,
15 ms
asset_70de176c7c1463d7f1018f172ca02529.js
957 ms
asset_d13d319bc873659629c3a2cbdef25fe8.js
960 ms
asset_3abb9ca668f9c2ab539911c3b4ae978b.js
910 ms
asset_4d8fa64057663d9acfe089638a392983.js
910 ms
asset_f47692b2afbef679e8753bd4289c614b.js
911 ms
asset_78817e9c207b2f1a08cf7b0639b7a05c.js
1042 ms
asset_73a417c8cdd742c830116e0c195fe726.js
1068 ms
asset_62397165ca3be6b40aaea295f956cae3.js
1069 ms
asset_675f3f11428820f6266e8bc5a28b5f4c.js
1068 ms
asset_7e844de5505cbc4e2675d0797ddfb028.js
1067 ms
asset_2c301638fe9bcbc75898e98c6b144df0.js
1090 ms
logo-carte.svg
1330 ms
gtm.js
432 ms
phone-left.png
695 ms
phone-right.png
695 ms
analytics.js
122 ms
blur-up.js
357 ms
lazysizes.js
350 ms
SFProDisplay-Regular.woff
590 ms
SFProDisplay-Medium.woff
286 ms
SFProDisplay-Semibold.woff
795 ms
SFProDisplay-Bold.woff
494 ms
SFProDisplay-Heavy.woff
792 ms
rtrg
701 ms
client.js
492 ms
collect
28 ms
c1cd4cc38acf8e8849f2f2b2840904---png_20x12:whitepadding1:quality20_c1024_convert.png
1146 ms
c1cd4cc38acf8e8849f2f2b2840904---png_700x385:center:whitepadding15_6baba_convert.png
1908 ms
24941855ca2d7c1d2a6d5e84807b7c---png_20x12:whitepadding1:quality20_c1024_convert.png
1138 ms
24941855ca2d7c1d2a6d5e84807b7c---png_700x385:center:whitepadding15_6baba_convert.png
1891 ms
collect
399 ms
ga-audiences
514 ms
28cb56f382c01ae021d9a3acca8112---png_20x12:whitepadding1:quality20_c1024_convert.png
307 ms
28cb56f382c01ae021d9a3acca8112---png_700x385:center:whitepadding15_6baba_convert.png
1653 ms
96d8c0f9fa972a0cf8ae19ed12ee2e---png_20x12:whitepadding1:quality20_c1024_convert.png
237 ms
96d8c0f9fa972a0cf8ae19ed12ee2e---png_700x385:center:whitepadding15_6baba_convert.png
964 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
Image elements do not have [alt] attributes
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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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: