14.1 sec in total
530 ms
8.7 sec
4.9 sec
Visit grand.bg now to see the best up-to-date Grand content and also check out these interesting facts you probably never knew about grand.bg
????????? ????? ?? ???????? ? ??? ???? ? ???????????, ????, ???????, ????? ? ????????? ????? ➤ SUPRIMMO ➤ ?? ?????? ???????? ????? ??? ?? ☎0883 700 335 / ☎0700 70 335
Visit grand.bgWe analyzed Grand.bg page load time and found that the first response time was 530 ms and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
grand.bg performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value12.7 s
0/100
25%
Value11.6 s
4/100
10%
Value2,030 ms
7/100
30%
Value0.002
100/100
15%
Value14.8 s
8/100
10%
530 ms
305 ms
1238 ms
30 ms
253 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Grand.bg, 63% (55 requests) were made to Superimoti.bg and 21% (18 requests) were made to Static4.superimoti.bg. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Superimoti.bg.
Page size can be reduced by 660.2 kB (31%)
2.1 MB
1.5 MB
In fact, the total size of Grand.bg main page is 2.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 527.8 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 110.0 kB, which is 18% 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 527.8 kB or 87% of the original size.
Potential reduce by 116.5 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. Grand images are well optimized though.
Potential reduce by 14.6 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 14.6 kB or 12% of the original size.
Potential reduce by 1.3 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. Grand.bg needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 19% of the original size.
Number of requests can be reduced by 35 (45%)
77
42
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grand. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and as a result speed up the page load time.
grand.bg
530 ms
www.superimoti.bg
305 ms
www.superimoti.bg
1238 ms
font-awesome.min.css
30 ms
custom.css
253 ms
jquery.fancybox.css
341 ms
jquery.2.2.3.min.js
456 ms
foundation.6.4.3.min.js
456 ms
slick.min.js
456 ms
navhide.js
560 ms
scrolltotop.js
563 ms
blazy.min.js
658 ms
sumoselect_v3.js
660 ms
base64.js
561 ms
jquery.fancybox.js
733 ms
seo.js
727 ms
custom.js
747 ms
custom_gdpr.js
746 ms
detect.js
749 ms
custom_newsletter.js
750 ms
search_engine_common_function.js
850 ms
search_engine_quick_clear.js
850 ms
ouibounce.js
851 ms
custom_subscribe_popup.js
851 ms
custom_bfv.js
850 ms
slick_controller_v2.js
881 ms
search_engine_simple_v7.js
960 ms
custom_list_complex.js
963 ms
custom_offers_tab_responsive_v2.js
974 ms
custom_rotate_banner_blazy.js
958 ms
tabs_ajax_mini.js
974 ms
jquery.autocomplete.js
1012 ms
search_engine_simple_clear.js
1107 ms
app.js
1114 ms
custom_extended_v2.js
3147 ms
360-svg-black2.svg
2931 ms
ru.svg
2933 ms
en.svg
2977 ms
de.svg
2986 ms
stoyanov_en_1c1d38.png
2987 ms
logo-bg.png
3146 ms
gtm.js
279 ms
eclipse.gif
3128 ms
fontawesome-webfont.woff
84 ms
GloberBG-Regular.woff
2763 ms
GloberBG-Bold.woff
2919 ms
GloberBG-SemiBold.woff
2867 ms
GloberBG-Black.woff
2812 ms
GloberBG-Heavy.woff
2813 ms
trans.png
2719 ms
menu-arrow.png
3012 ms
conversion_async.js
133 ms
analytics.js
161 ms
fbevents.js
161 ms
px.js
2648 ms
fa-arrow-down.png
2649 ms
GloberBG-Light.woff
2919 ms
121 ms
collect
33 ms
119523922046122
97 ms
collect
57 ms
63 ms
ga-audiences
25 ms
1677 ms
hot_offers1_responsive_v7.php
1083 ms
1662969249T105604_30.jpg
914 ms
1662969249T105604_1.jpg
1541 ms
1662969249T105604_2.jpg
1540 ms
1662969249T105604_3.jpg
2830 ms
1662727803T101870_1.jpg
1540 ms
1662727803T101870_2.jpg
1538 ms
1662727803T101870_3.jpg
1540 ms
1662727803T101870_4.jpg
2831 ms
1662727803T101870_5.jpg
2830 ms
1662727803T101870_6.jpg
2827 ms
1662969249T105604_4.jpg
1331 ms
1662969249T105604_5.jpg
1360 ms
1664262426T105604_30.jpg
1338 ms
1664181565T101870_1.jpg
1335 ms
1663933206T105765_1.jpg
1333 ms
1662640204T95273_1.jpg
1337 ms
1664278194T79570_1.jpg
1335 ms
1659075014T96641_1.jpg
1337 ms
logo-luximo-selection.png
1334 ms
ico-heart-o.svg
1329 ms
360-slider.webp
1332 ms
dst-wave-dark.svg
136 ms
grand.bg accessibility score
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-*] attributes do not match their roles
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
grand.bg 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
grand.bg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
BG
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grand.bg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Bulgarian language. Our system also found out that Grand.bg main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
grand.bg
Open Graph description is not detected on the main page of Grand. 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: