8.4 sec in total
1.1 sec
3.8 sec
3.5 sec
Visit whata.org now to see the best up-to-date Whata content for Bulgaria and also check out these interesting facts you probably never knew about whata.org
Архитектурата, списанията, киното и следобедната закуска - така както ги виждат четиримата архитекти от WhAT Association
Visit whata.orgWe analyzed Whata.org page load time and found that the first response time was 1.1 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
whata.org performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value3.9 s
54/100
25%
Value2.7 s
96/100
10%
Value220 ms
88/100
30%
Value0.26
47/100
15%
Value3.5 s
92/100
10%
1071 ms
96 ms
594 ms
47 ms
225 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 90% of them (112 requests) were addressed to the original Whata.org, 4% (5 requests) were made to Google.com and 2% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Whata.org.
Page size can be reduced by 1.3 MB (11%)
11.7 MB
10.4 MB
In fact, the total size of Whata.org main page is 11.7 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. Only a small number of websites need less resources to load. Images take 11.3 MB which makes up the majority of the site volume.
Potential reduce by 158.2 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 158.2 kB or 74% of the original size.
Potential reduce by 1.1 MB
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. Whata images are well optimized though.
Potential reduce by 1.0 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 15.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. Whata.org needs all CSS files to be minified and compressed as it can save up to 15.7 kB or 59% of the original size.
Number of requests can be reduced by 7 (6%)
119
112
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whata. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
whata.org
1071 ms
js
96 ms
shortlog5.css
594 ms
css
47 ms
logo.svg
225 ms
3586t.png
605 ms
mob-2.jpg
679 ms
3579t.jpg
604 ms
3554t.jpg
605 ms
3550t.jpg
607 ms
3551t.jpg
681 ms
3552t.jpg
532 ms
3549t.jpg
755 ms
3555t.jpg
781 ms
3556t.jpg
933 ms
3557t.jpg
820 ms
3558t.jpg
941 ms
3559t.jpg
862 ms
3561t.jpg
868 ms
3560t.jpg
893 ms
3562t.jpg
1055 ms
3563t.jpg
976 ms
3564t.jpg
981 ms
3565t.jpg
1116 ms
3567t.jpg
1049 ms
3568t.jpg
1175 ms
3569t.jpg
1088 ms
3575t.jpg
1093 ms
3571t.jpg
1166 ms
3572t.jpg
1173 ms
3573t.jpg
1200 ms
3574t.jpg
1207 ms
3534t.jpg
1229 ms
3547t.jpg
1283 ms
3526t.jpg
1291 ms
3539t.jpg
1409 ms
3536t.jpg
1312 ms
3537t.jpg
1319 ms
3535t.jpg
1121 ms
3544t.jpg
1168 ms
cse.js
156 ms
3548t.png
1038 ms
EJRVQgYoZZY2vCFuvAFbzro.ttf
132 ms
EJRSQgYoZZY2vCFuvAnt66qfVy4.ttf
204 ms
EJRTQgYoZZY2vCFuvAFT_rC1dw.ttf
278 ms
cse_element__bg.js
27 ms
default+bg.css
91 ms
default.css
101 ms
async-ads.js
96 ms
branding.png
22 ms
3542t.jpg
898 ms
clear.png
56 ms
3512t.jpg
836 ms
3508t.jpg
855 ms
3523t.jpg
920 ms
3501t.jpg
857 ms
3499t.jpg
865 ms
3502t.jpg
808 ms
3500t.jpg
797 ms
3497t.jpg
791 ms
3505t.jpg
821 ms
3506t.jpg
790 ms
3507t.jpg
787 ms
3511t.jpg
770 ms
3503t.jpg
739 ms
3516t.png
855 ms
3514t.png
784 ms
3519t.jpg
789 ms
3521t.jpg
716 ms
3518t.jpg
721 ms
3452.png
1059 ms
3494t.jpg
784 ms
3461t.jpg
762 ms
3463t.jpg
723 ms
3465t.jpg
717 ms
3464t.jpg
733 ms
3467t.jpg
795 ms
3481t.jpg
784 ms
3468t.jpg
779 ms
3453t.jpg
718 ms
3469t.jpg
728 ms
3470t.jpg
791 ms
3474t.jpg
792 ms
3473t.jpg
774 ms
3455t.jpg
840 ms
3475t.jpg
723 ms
3483t.jpg
790 ms
3487t.jpg
799 ms
3490t.jpg
797 ms
3486t.jpg
791 ms
3454t.jpg
744 ms
3482t.jpg
799 ms
3476t.jpg
809 ms
3478t.jpg
796 ms
3479t.jpg
812 ms
3485t.jpg
791 ms
3492t.jpg
745 ms
3449t.png
792 ms
3446t.jpg
806 ms
3427t.jpg
805 ms
3030t.jpg
804 ms
3415t.jpg
724 ms
3020t.jpg
737 ms
3021t.jpg
787 ms
3024t.jpg
798 ms
3428t.jpg
792 ms
3416t.jpg
711 ms
3418t.jpg
723 ms
3422t.jpg
732 ms
3419t.jpg
779 ms
3417t.jpg
778 ms
3431t.jpg
713 ms
3420t.jpg
705 ms
3412.jpg
833 ms
3413.jpg
734 ms
3414t.jpg
763 ms
3044t.jpg
696 ms
1666.gif
123 ms
tw.gif
119 ms
1670.gif
216 ms
1671.gif
206 ms
comment.gif
251 ms
fb-t1.gif
238 ms
blog-print.css
114 ms
whata.org 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.
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
whata.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
whata.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
![]()
N/A
![]()
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whata.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Bulgarian. Our system also found out that Whata.org 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.
whata.org
Open Graph description is not detected on the main page of Whata. 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: