10.7 sec in total
1.2 sec
9.4 sec
95 ms
Visit whatshot.ro now to see the best up-to-date Whatshot content and also check out these interesting facts you probably never knew about whatshot.ro
Petrecerile cele mai hot, in fiecare club tare din Bucuresti. Noapte de noapte, pana la 5 dimineata. In weekend, cand esti la munte sau la mare, stii ce evenimente sunt prin cluburi din Brasov, Predea...
Visit whatshot.roWe analyzed Whatshot.ro page load time and found that the first response time was 1.2 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
whatshot.ro performance score
1202 ms
201 ms
286 ms
296 ms
295 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 53% of them (40 requests) were addressed to the original Whatshot.ro, 12% (9 requests) were made to Google.com and 12% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Whatshot.ro.
Page size can be reduced by 348.9 kB (52%)
670.8 kB
321.9 kB
In fact, the total size of Whatshot.ro main page is 670.8 kB. 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. Javascripts take 383.4 kB which makes up the majority of the site volume.
Potential reduce by 33.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. 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 33.7 kB or 78% of the original size.
Potential reduce by 26.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. Obviously, Whatshot needs image optimization as it can save up to 26.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 258.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 258.9 kB or 68% of the original size.
Potential reduce by 29.6 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. Whatshot.ro needs all CSS files to be minified and compressed as it can save up to 29.6 kB or 84% of the original size.
Number of requests can be reduced by 38 (53%)
72
34
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatshot. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
whatshot.ro
1202 ms
style.css
201 ms
additional.css
286 ms
highslide.css
296 ms
nivo-slider.css
295 ms
highslide-with-html.js
484 ms
jquery-1.4.3.min.js
463 ms
jquery.nivo.slider.js
388 ms
jquery.twiterLikePagination.js
437 ms
challenge
26 ms
challenge
51 ms
logo.gif
178 ms
bng.png
199 ms
bands_minus.png
204 ms
bands.png
196 ms
stand%20up%20comedy_5405.jpg
266 ms
afis%20equinoxe_5406.jpg
429 ms
karaokegirl_2275.jpg
434 ms
karaoke-madness_2276.jpg
632 ms
theginfactory1_2900.jpg
434 ms
tribut_2901.jpg
643 ms
princessclub1_3916.jpg
498 ms
CASINO_3917.jpg
704 ms
mail.png
565 ms
facebook.png
567 ms
twitter.png
662 ms
telefon.png
703 ms
rss.gif
708 ms
green.gif
768 ms
plusone.js
90 ms
green_down.gif
767 ms
yellow_small.png
779 ms
yellow_down_small.png
833 ms
shots_gray.gif
822 ms
munte.gif
825 ms
mare.gif
894 ms
gray.png
899 ms
recaptcha.js
17 ms
fdNPhfiab-XXWFZC4cs1ZwRW1YVuobzzx0F9p6k9YN8.js
4 ms
ga.js
29 ms
piwik.js
941 ms
refresh.gif
23 ms
audio.gif
18 ms
text.gif
19 ms
help.gif
18 ms
like.php
287 ms
__utm.gif
27 ms
cb=gapi.loaded_0
17 ms
cb=gapi.loaded_1
15 ms
fastbutton
108 ms
like.php
216 ms
postmessageRelay
53 ms
like.php
268 ms
like.php
187 ms
reload
51 ms
3193398744-postmessagerelay.js
53 ms
rpc:shindig_random.js
54 ms
rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ
9 ms
cb=gapi.loaded_0
30 ms
cb=gapi.loaded_1
30 ms
image
18 ms
cb=gapi.loaded_0
8 ms
Dt46LmMjzaB.js
29 ms
LVx-xkvaJ0b.png
20 ms
Dt46LmMjzaB.js
20 ms
Dt46LmMjzaB.js
59 ms
Dt46LmMjzaB.js
56 ms
Dt46LmMjzaB.js
21 ms
Dt46LmMjzaB.js
19 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
26 ms
zoomin.cur
153 ms
piwik.php
6386 ms
drop-shadow.png
287 ms
zoomout.cur
282 ms
loader.white.gif
287 ms
whatshot.ro SEO score
RO
RO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatshot.ro can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Whatshot.ro 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.
whatshot.ro
Open Graph description is not detected on the main page of Whatshot. 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: