2.6 sec in total
33 ms
2.1 sec
427 ms
Click here to check amazing Whosay content for United States. Otherwise, check out these important facts you probably never knew about whosay.com
Paramount is one of the world’s leading producers of premium entertainment content that connects billions of people in nearly every country in the world.
Visit whosay.comWe analyzed Whosay.com page load time and found that the first response time was 33 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
whosay.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value22.4 s
0/100
25%
Value9.4 s
12/100
10%
Value1,520 ms
14/100
30%
Value0.002
100/100
15%
Value17.2 s
5/100
10%
33 ms
19 ms
159 ms
174 ms
68 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 6% of them (7 requests) were addressed to the original Whosay.com, 50% (56 requests) were made to Media2.whosaystatic.com and 4% (5 requests) were made to Cdn1.whosaystatic.com. The less responsive or slowest element that took the longest time to load (662 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 1.4 MB (51%)
2.7 MB
1.3 MB
In fact, the total size of Whosay.com main page is 2.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. 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 202.3 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 202.3 kB or 87% of the original size.
Potential reduce by 0 B
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. Whosay images are well optimized though.
Potential reduce by 872.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 872.0 kB or 69% of the original size.
Potential reduce by 290.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. Whosay.com needs all CSS files to be minified and compressed as it can save up to 290.7 kB or 74% of the original size.
Number of requests can be reduced by 30 (30%)
101
71
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whosay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
whosay.com
33 ms
www.whosay.com
19 ms
Modernizr-2.8.3.min.js
159 ms
main.d0af7119.css
174 ms
css
68 ms
main.min.19a6e9b2.js
172 ms
oct.js
58 ms
adsct
566 ms
adsct
344 ms
sdk.js
650 ms
widgets.js
340 ms
gpt.js
297 ms
fan
277 ms
pinit.js
276 ms
quant.js
79 ms
beacon.js
80 ms
analytics.js
79 ms
fbds.js
438 ms
channels
185 ms
accounts
78 ms
topposts
117 ms
toadOcfmlt9b38dHJxOBGFP7R5lD_au4SZC6Ks_vyWs.ttf
375 ms
ODelI1aHBYDBqgeIAH2zlNRl0pGnog23EMYRrBmUzJQ.ttf
590 ms
toadOcfmlt9b38dHJxOBGOiMeWyi5E_-XkTgB5psiDg.ttf
662 ms
whosay-icons.2650c57c1a.woff
59 ms
pubads_impl_81.js
258 ms
controltag
255 ms
454949_85x85.jpg
319 ms
138479_85x85.jpg
307 ms
850093_85x85.jpg
305 ms
283576_85x85.jpg
307 ms
35485_85x85.jpg
309 ms
720743_85x85.jpg
309 ms
890845_85x85.jpg
309 ms
544919_85x85.jpg
312 ms
736584_85x85.jpg
311 ms
8541_85x85.jpg
314 ms
762052_85x85.jpg
313 ms
430147_85x85.jpg
312 ms
890898_50x50.jpg
251 ms
891000_370x370.jpg
253 ms
347680_50x50.jpg
249 ms
890990_370x370.jpg
251 ms
645164_50x50.jpg
249 ms
890989_370x370.jpg
252 ms
817597_50x50.jpg
253 ms
889749_570x570.jpg
360 ms
890997_435x292.jpg
186 ms
890951_174x117.jpg
184 ms
890901_174x117.jpg
185 ms
890858_174x117.jpg
185 ms
890872_435x292.jpg
186 ms
890849_174x117.jpg
186 ms
890802_174x117.jpg
283 ms
890329_174x117.jpg
284 ms
890954_435x292.jpg
285 ms
890046_174x117.jpg
285 ms
890889_174x117.jpg
286 ms
890863_174x117.jpg
286 ms
editorial
125 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
449 ms
pixel;r=512095456;a=p-fMCwz08zt24YX;fpan=1;fpa=P0-672732631-1456764363340;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456764363339;tzo=-180;ref=;url=http%3A%2F%2Fwww.whosay.com%2F;ogl=site_name.WhoSay%2Ctitle.WhoSay%20-%20Social%20Celebrities%252C%20Entertainment%20News%252C%20Photos%252C%20Videos%252C%20and%20Exclusives%2Curl.http%3A%2F%2Fwww%252Ewhosay%252Ecom%2F%2Ctype.website%2Cdescription.Get%20the%20latest%20photos%252C%20videos%20and%20news%252C%20directly%20from%20your%20favorite%20celebrities%252C%2Cimage.http%3A%2F%2Fcdn1%252Ewhosaystatic%252Ecom%2Fapp%2Fwww%2Fassets%2Fimages%2Flarge_og_logo%252Epng%2Cimage%3Awidth.1200%2Cimage%3Aheight.630
104 ms
collect
94 ms
collect
97 ms
890997_370x250.jpg
160 ms
890951_147x99.jpg
161 ms
890901_147x99.jpg
160 ms
890858_147x99.jpg
162 ms
collect
388 ms
890872_370x250.jpg
227 ms
890849_147x99.jpg
227 ms
890802_147x99.jpg
226 ms
890329_147x99.jpg
225 ms
890954_370x250.jpg
226 ms
890046_147x99.jpg
223 ms
890889_147x99.jpg
226 ms
890863_147x99.jpg
224 ms
890802_435x292.jpg
221 ms
890901_435x292.jpg
223 ms
890819_435x292.jpg
223 ms
890046_435x292.jpg
221 ms
890858_435x292.jpg
225 ms
890842_435x292.jpg
226 ms
890802_370x250.jpg
122 ms
890901_370x250.jpg
121 ms
890819_370x250.jpg
120 ms
890046_770x517.jpg
120 ms
890858_370x250.jpg
182 ms
890842_370x250.jpg
182 ms
Voltaire.woff
93 ms
pinit_main.js
153 ms
container.html
147 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
146 ms
162 ms
ads
124 ms
53 ms
xd_arbiter.php
142 ms
xd_arbiter.php
255 ms
ga-audiences
46 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
59 ms
ads
31 ms
ads
30 ms
optout_check
59 ms
get
99 ms
genericusersync.ashx
36 ms
39 ms
generic
35 ms
29 ms
jot
93 ms
generic
32 ms
like.php
76 ms
vpc6VNjRPXV.js
287 ms
LVx-xkvaJ0b.png
321 ms
whosay.com 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
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
whosay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Page has valid source maps
whosay.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whosay.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Whosay.com main page’s claimed encoding is iso-8859-1. 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.
whosay.com
Open Graph data is detected on the main page of Whosay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: