8.7 sec in total
27 ms
1.9 sec
6.8 sec
Click here to check amazing Somethinelse content for United Kingdom. Otherwise, check out these important facts you probably never knew about somethinelse.com
We are the Global Podcast Division of Sony Music Entertainment, based in New York, Los Angeles and London. Through our creator-first philosophy and diverse international partnerships we produce premiu...
Visit somethinelse.comWe analyzed Somethinelse.com page load time and found that the first response time was 27 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
somethinelse.com performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value3.8 s
54/100
25%
Value2.4 s
98/100
10%
Value1,680 ms
11/100
30%
Value0.053
98/100
15%
Value6.9 s
54/100
10%
27 ms
210 ms
48 ms
48 ms
148 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 37% of them (19 requests) were addressed to the original Somethinelse.com, 47% (24 requests) were made to Cdn-p.smehost.net and 4% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cdn-p.smehost.net.
Page size can be reduced by 305.8 kB (1%)
21.3 MB
21.0 MB
In fact, the total size of Somethinelse.com main page is 21.3 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. 60% of websites need less resources to load. Images take 21.0 MB which makes up the majority of the site volume.
Potential reduce by 108.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. 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 108.9 kB or 75% of the original size.
Potential reduce by 196.4 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. Somethinelse images are well optimized though.
Potential reduce by 67 B
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 423 B
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. Somethinelse.com has all CSS files already compressed.
Number of requests can be reduced by 13 (28%)
46
33
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Somethinelse. 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 7 to 1 for CSS and as a result speed up the page load time.
somethinelse.com
27 ms
somethinelse.com
210 ms
landing.css
48 ms
style.min.css
48 ms
admin-style-7b635867.css
148 ms
front.min.css
47 ms
style.css
44 ms
css
34 ms
main.css
51 ms
front.min.js
64 ms
jquery.min.js
62 ms
jquery-migrate.min.js
72 ms
email-decode.min.js
58 ms
main.js
74 ms
aos.js
34 ms
aos.js
24 ms
analytics.js
115 ms
SONY-HOW-TO-FAIL-3000x3000-1.jpg
1057 ms
image003.jpg
259 ms
MicrosoftTeams-image-44.jpg
544 ms
MicrosoftTeams-image-53.jpg
278 ms
image003-1.jpg
1414 ms
OTL_s9_.jpg
274 ms
Vector-150x107.png
602 ms
Rescue.jpeg
522 ms
OTLAE.jpg
412 ms
What-a-Combo.png
631 ms
YHMAH.jpg
667 ms
Screenshot-2023-07-17-at-12.41.42.png
684 ms
MicrosoftTeams-image-69.jpg
874 ms
MicrosoftTeams-image-31.jpg
764 ms
image001.jpg
825 ms
MicrosoftTeams-image-54.jpg
823 ms
MicrosoftTeams-image-45.jpg
970 ms
p0byxlps.jpg
1023 ms
MicrosoftTeams-image-37.jpg
984 ms
image002.png
1033 ms
JSYS.jpg
1116 ms
sonymusic.png
1140 ms
Picture1.png
1443 ms
logo-black-2-e1643118915922.png
1168 ms
site-logo.png
110 ms
spotify.svg
224 ms
apple-podcast.svg
220 ms
sprite-social-icons-70px.png
127 ms
brand-logo-circle.png
118 ms
sprite-social-icons-gray.png
119 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
25 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
35 ms
collect
19 ms
js
63 ms
somethinelse.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
somethinelse.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
somethinelse.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Somethinelse.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 Somethinelse.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.
somethinelse.com
Open Graph data is detected on the main page of Somethinelse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: