1.7 sec in total
138 ms
607 ms
1 sec
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 138 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
whosay.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value6.9 s
6/100
25%
Value6.6 s
37/100
10%
Value1,440 ms
15/100
30%
Value0.019
100/100
15%
Value19.3 s
2/100
10%
138 ms
36 ms
18 ms
56 ms
17 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Whosay.com, 63% (30 requests) were made to Paramount.com and 15% (7 requests) were made to Prod-acquia.viacomcbs.com. The less responsive or slowest element that took the longest time to load (268 ms) relates to the external source Prod-acquia.viacomcbs.com.
Page size can be reduced by 887.9 kB (17%)
5.1 MB
4.2 MB
In fact, the total size of Whosay.com main page is 5.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. 70% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 36.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 36.7 kB or 77% of the original size.
Potential reduce by 46.2 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. Whosay images are well optimized though.
Potential reduce by 478.8 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 478.8 kB or 52% of the original size.
Potential reduce by 326.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. Whosay.com needs all CSS files to be minified and compressed as it can save up to 326.3 kB or 74% of the original size.
Number of requests can be reduced by 12 (33%)
36
24
The browser has sent 36 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 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
whosay.com
138 ms
advertising
36 ms
advertising
18 ms
api.js
56 ms
css_o-Lu9vaCI_CLDlJYYyOqIc-V5uXS6e3ApafQwE07hSI.css
17 ms
css_P2iFXaEm5vFWQDlV8uUGonCSRBelLiNKC9gKXLKieQw.css
55 ms
paramount-stylesheet.css
67 ms
css_XB9n5L2n02_V2iRRVgZkLTfaBQu_ZiDhUE-kaaxVVIM.css
32 ms
js_uJw2q89HPUqbnb3SJM1-ikA1fJDCRpc7jRFgvzoNJ6k.js
53 ms
js_u9Rw-lELdqrv963h6woY36aOjX-Z2PLUbITv1jk-TNA.js
116 ms
gtm.js
53 ms
gtag.js
30 ms
js_kL6vvSFbtek5Qc60KQX6i7y3NYe1oGBl4L5iIEgokyU.js
64 ms
recaptcha__en.js
101 ms
utag.js
179 ms
logo%5B1%5D.svg
37 ms
Header_Desktop_Mountain_1920x1080.jpg
134 ms
Header_Mountain_Mobile_1080x1920_V01.jpg
40 ms
CBSSports_V02_1920x1440.jpg
145 ms
Mobile_CBSSPORTS_V02_767x767.jpg
140 ms
Halo_V02_1920x1440.jpg
134 ms
HALO_ATTRIBUTION_1024X1024.jpg
145 ms
VMAs_V02_1920x1440.jpg
144 ms
VMAS_ATTRIBUTION_1024X1024.jpg
141 ms
Lioness_Desktop_1920x1440_V03.jpg
142 ms
Lioness_Mobile_767x767_V03.jpg
165 ms
A_Force_of_Nature_416x234_DT.png
177 ms
A_Force_of_Nature_416x234_MB.png
183 ms
thepeak_The_Golazo_Effect416x234.png
155 ms
thepeak_The_Golazo_Effect767x432.png
155 ms
Ad-Sales-Popularity_Desktop_416x234_V3.jpg
180 ms
Ad-Sales-Popularity-Mobile-767x432_V3.jpg
175 ms
LinkedIn%5B1%5D.svg
175 ms
X%5B1%5D.svg
190 ms
paramount_logo%20%281%29.png
195 ms
PeakSans-Regular.woff
219 ms
PeakSans-Light.woff
268 ms
PeakSans-Semibold.woff
253 ms
PeakSans-Bold.woff
232 ms
PeakSans-Black.woff
253 ms
fallback
32 ms
ParamountVistaSans-CondensedBold.woff
112 ms
ParamountVistaSans-CondensedRegular.woff
146 ms
fallback__ltr.css
3 ms
css
37 ms
logo_48.png
4 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
31 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
31 ms
whosay.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
whosay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
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
EN
EN
UTF-8
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 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.
whosay.com
Open Graph description is not detected on the main page of Whosay. 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: