6.8 sec in total
1.3 sec
5 sec
464 ms
Welcome to whiz.bg homepage info - get ready to check Whiz best content for Bulgaria right away, or after learning these important things about whiz.bg
Създаваме висококачествени, модерни и печеливши native мобилни приложения и цялостни уеб решения за успеха на Вашия бизнес. Запознайте се с Whiz.
Visit whiz.bgWe analyzed Whiz.bg page load time and found that the first response time was 1.3 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
whiz.bg performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value11.1 s
0/100
25%
Value8.1 s
21/100
10%
Value1,520 ms
13/100
30%
Value0
100/100
15%
Value11.1 s
20/100
10%
1294 ms
84 ms
176 ms
232 ms
233 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 89% of them (116 requests) were addressed to the original Whiz.bg, 3% (4 requests) were made to Facebook.com and 2% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Whiz.bg.
Page size can be reduced by 954.9 kB (15%)
6.4 MB
5.4 MB
In fact, the total size of Whiz.bg main page is 6.4 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 5.2 MB which makes up the majority of the site volume.
Potential reduce by 59.9 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 8.8 kB, which is 13% 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 59.9 kB or 85% of the original size.
Potential reduce by 93.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. Whiz images are well optimized though.
Potential reduce by 508.5 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 508.5 kB or 70% of the original size.
Potential reduce by 292.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. Whiz.bg needs all CSS files to be minified and compressed as it can save up to 292.8 kB or 86% of the original size.
Number of requests can be reduced by 36 (28%)
129
93
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whiz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.whiz.bg
1294 ms
jquery.nouislider.css
84 ms
common.css
176 ms
desktop_1920.css
232 ms
projects.css
233 ms
jquery-1.11.2.min.js
356 ms
jquery-ui.js
566 ms
jquery.event.move.js
252 ms
jquery.event.swipe.js
254 ms
common.js
307 ms
slider.js
308 ms
jquery.nouislider.all.js
450 ms
platform.js
67 ms
js
53 ms
map.js
351 ms
services.css
227 ms
dc.js
122 ms
analytics.js
81 ms
fbds.js
70 ms
desktop_1366.css
95 ms
sdk.js
89 ms
img_logo_whiz.png
109 ms
ic_arrow_white.png
110 ms
ic_flag_en.png
111 ms
preloader.gif
181 ms
img_samsonite_store_home_hero_1920.jpg
480 ms
img_samsonite_store_home_hero_768.jpg
478 ms
img_samsonite_store_home_hero_640.jpg
327 ms
img_samsonite_store_home_hero_360.jpg
345 ms
ic_project_desktop_dark.png
183 ms
ic_project_plus_dark.png
263 ms
ic_project_tablet_dark.png
266 ms
ic_project_smartphone_dark.png
345 ms
img_logo_samsonite_store.png
353 ms
img_logo_fibank_banner.png
404 ms
img_fibank_home_hero_android.png
426 ms
img_fibank_home_hero_iphone.png
428 ms
img_logo_hero_16_gong.png
429 ms
img_logo_sinoptik.png
479 ms
img_logo_bricolage.png
508 ms
img_bricolage_home_device1.png
752 ms
img_logo_zora.png
511 ms
img_bricolage_home_hero_device.png
720 ms
img_darik_logo.png
556 ms
ic_arrow_header_nav_left.png
557 ms
ic_arrow_header_nav_right.png
589 ms
img_logo_client_1_fibank.png
574 ms
img_logo_client_3_mastercard.png
615 ms
img_logo_client_bricolage.png
616 ms
img_logo_client_4_zora.png
652 ms
img_logo_client_8_bayer.png
655 ms
img_logo_client_5_samsonite.png
691 ms
img_logo_client_2_bet365.png
692 ms
img_logo_client_kamenitza.png
735 ms
img_logo_client_26_katarzyna.png
736 ms
ic_arrow_grey.png
767 ms
112 ms
collect
25 ms
collect
54 ms
img_shadow.png
685 ms
ic_service_websites_normal.png
697 ms
ic_service_plus.png
727 ms
93 ms
97 ms
__utm.gif
15 ms
ic_service_ecommerce_normal.png
700 ms
xd_arbiter.php
35 ms
ic_service_mobile_apps_normal.png
660 ms
ic_service_facebook_normal.png
685 ms
ic_service_software_normal.png
601 ms
ic_service_strategy_normal.png
619 ms
ic_quote.png
590 ms
testimonial_bricolage.png
573 ms
testimonial_zora.png
574 ms
img_logo_fibank.png
588 ms
btn_reference_nav_left_normal.png
539 ms
btn_reference_nav_right_normal.png
539 ms
img_katarzyna_home_banner_1920.jpg
571 ms
img_katarzyna_home_banner_default.jpg
651 ms
img_logo_katarzyna.png
524 ms
ic_arrow_black.png
538 ms
img_piquadro_home_banner_1920.jpg
539 ms
img_piquadro_home_banner_default.jpg
539 ms
ic_project_desktop_white.png
571 ms
ic_project_plus_white.png
524 ms
ic_project_tablet_white.png
534 ms
ic_project_smartphone_white.png
506 ms
img_logo_piquadro.png
543 ms
ic_contacts_footer_mail.png
530 ms
ic_contacts_footer_phone.png
531 ms
ic_contacts_footer_mobile.png
495 ms
ic_contacts_footer_address.png
495 ms
btn_social_fb_normal.png
462 ms
btn_social_twitter_normal.png
506 ms
btn_social_g+_normal.png
524 ms
desktop_1280.css
85 ms
desktop_1024.css
87 ms
tablet_landscape.css
87 ms
tablet_portrait.css
86 ms
smartphone_landscape.css
87 ms
smartphone_portrait.css
86 ms
20 ms
img_fibank_home_hero_1920.jpg
88 ms
img_fibank_home_hero_768.jpg
228 ms
img_fibank_home_hero_640.jpg
164 ms
img_fibank_home_hero_360.jpg
165 ms
ic_project_ios_dark.png
85 ms
ic_project_android_dark.png
79 ms
img_gong_home2_hero_1920.jpg
309 ms
img_gong_home_hero_768.jpg
328 ms
img_gong_home_hero_640.jpg
248 ms
img_gong_home_hero_360.jpg
326 ms
ic_project_ios_white.png
246 ms
ic_project_android_white.png
303 ms
img_sinoptik_home_hero_1920.jpg
574 ms
img_sinoptik_home_hero_768.jpg
412 ms
img_sinoptik_home_hero_640.jpg
454 ms
img_sinoptik_home_hero_360.jpg
384 ms
img_bricolage_home_hero_1920.jpg
489 ms
img_bricolage_home_hero_768.jpg
492 ms
img_bricolage_home_hero_640.jpg
463 ms
img_bricolage_home_hero_360.jpg
493 ms
img_zora_home_hero_1920.jpg
683 ms
img_zora_home_hero_768.jpg
540 ms
img_zora_home_hero_640.jpg
571 ms
img_zora_home_hero_360.jpg
575 ms
img_darik_home_hero_1920.jpg
817 ms
img_darik_home_hero_768.jpg
617 ms
img_darik_home_hero_640.jpg
656 ms
img_darik_home_hero_360.jpg
655 ms
whiz.bg 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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
whiz.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
Browser errors were logged to the console
whiz.bg 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
BG
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whiz.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whiz.bg 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.
whiz.bg
Open Graph description is not detected on the main page of Whiz. 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: