2.1 sec in total
859 ms
1.2 sec
82 ms
Visit b93.com now to see the best up-to-date B 93 content for United States and also check out these interesting facts you probably never knew about b93.com
Michigan's #1 For NEW Country
Visit b93.comWe analyzed B93.com page load time and found that the first response time was 859 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
b93.com performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value5.3 s
21/100
25%
Value17.6 s
0/100
10%
Value8,510 ms
0/100
30%
Value0.329
35/100
15%
Value41.5 s
0/100
10%
859 ms
53 ms
58 ms
60 ms
60 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original B93.com, 3% (2 requests) were made to Z.moatads.com and 3% (2 requests) were made to I.iheart.com. The less responsive or slowest element that took the longest time to load (859 ms) relates to the external source B93.iheart.com.
Page size can be reduced by 1.2 MB (60%)
2.0 MB
816.7 kB
In fact, the total size of B93.com main page is 2.0 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. HTML takes 1.2 MB which makes up the majority of the site volume.
Potential reduce by 1.0 MB
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 1.0 MB or 82% of the original size.
Potential reduce by 2.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. Obviously, B 93 needs image optimization as it can save up to 2.4 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 193.1 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 193.1 kB or 26% of the original size.
Potential reduce by 1.4 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. B93.com has all CSS files already compressed.
Number of requests can be reduced by 50 (88%)
57
7
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of B 93. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
b93.iheart.com
859 ms
bundle.8b37dfa4e56540828535.css
53 ms
local.bc06f128f534d4a5d747.css
58 ms
core-components-tiles-OnairTileLoader-component.12f62d6d6ad5771d626e.css
60 ms
core-page-blocks-datasource-DatasourceLoader-component.ed118ca85e0cefc658b6.css
60 ms
Datasource-component.a1eb25fbdc158e499608.css
66 ms
Grid-component.9e05f3f8fa0e6b993347.css
65 ms
components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css
63 ms
core-page-blocks-music-MusicTile-component.c0f2337b7d57cb7e8b6d.css
62 ms
Heading-component.d79a5c95e6ef67a97bca.css
61 ms
Show-component.608ec1ff0656c8b676a1.css
63 ms
LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css
65 ms
core-page-blocks-datasource-DatasourceTileLoader-component.a1eb25fbdc158e499608.css
68 ms
FauxButton-component.1f25bb623660eb4f88c1.css
70 ms
Eyebrow-component.23e83d8b8cab22ea99d6.css
69 ms
components-catalog-TrackList-component.626e2b289929900208bd.css
71 ms
Podcasts-component.570accd833088f4c4e7d.css
65 ms
ImageTile-component.c2cbd469fbc0bd11cbdf.css
71 ms
Card-component.c66d212af09897afcdd6.css
73 ms
AptivadaKeywordContest-component.a21f13419d9d48bf409a.css
74 ms
sdk.js
68 ms
moatheader.js
69 ms
ebx.js
221 ms
runtime.214e6c876f50b2a8a6a2.js
59 ms
vendor.82993fc136b73cc6a6f2.js
125 ms
bundle.60f9f8edb929059ddf6f.js
208 ms
packages-renderer-shared-ui-src-elements-MagicLink-component.748e878b4b4ef9b70e33.js
59 ms
src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_HeaderSearch_component_tsx-src_-b801d3.ebb7c95d698279b1c9ec.js
122 ms
local.a5b480bb028a49b07c6c.js
122 ms
core-components-tiles-OnairTileLoader-component.3c9c776801ce3f5ccf05.js
123 ms
core-page-blocks-datasource-DatasourceLoader-component.be189e440f36a30fac9f.js
122 ms
packages_renderer_shared_core_src_lib_ads_ts.1c411bb05fe7a8d6fb44.js
127 ms
Datasource-component.09c541938624ea67842c.js
128 ms
Grid-component.48dae21730bceb9ee5e7.js
127 ms
ContentFeedItem-component.2c07f0e7be984e8aee02.js
127 ms
LeadFeedItem-component.4330af319e52f7557387.js
128 ms
components-tiles-ContentTile-component.22ddd6a7b1c8a1bc4e2d.js
186 ms
core-page-blocks-music-MusicTile-component.1e79eaaa9e2979d88ec8.js
189 ms
ShowCollection-component.0c3f9b3068fe83748412.js
187 ms
Heading-component.ea88c81b8d34c977158c.js
187 ms
Show-component.cdfd0315af774eaef8dd.js
155 ms
core-page-blocks-podcast-PodcastsLoader-component.71edb632222c77f48f93.js
152 ms
LoadMoreFromCursor-component.dd840a1844d3d6bb0d7d.js
152 ms
core-page-blocks-datasource-DatasourceTileLoader-component.70fbc1958e35a8aed3b5.js
158 ms
FauxButton-component.6f17f4f82d52801c5c49.js
151 ms
core-page-blocks-contest-KeywordContestLoader-component.eb063dc982e7b1285f9b.js
152 ms
Eyebrow-component.533482f1ba2c4fcd4202.js
151 ms
components-catalog-TrackList-component.04f8bfd3f9d530b10dfd.js
154 ms
DateTimeDisplay-component.baa2bb00da4f804350fd.js
153 ms
vendors-node_modules_pnpm_isomorphic-dompurify_0_23_0_node_modules_isomorphic-dompurify_browser_js.6c4667c6ebbb3bd5aea7.js
156 ms
Podcasts-component.c822825f35d41178cdf7.js
151 ms
ImageTile-component.b3ff14a77346457b64fe.js
153 ms
Card-component.24dee8840408569eb2c3.js
153 ms
AptivadaKeywordContest-component.b7ea73f8063fca6968f6.js
152 ms
360057661571
210 ms
5e6ab48547247f68ba8de476
186 ms
f79fc341-a979-4863-81b0-eea1ddc6e07b
142 ms
v2
72 ms
n.js
60 ms
iframe.html
25 ms
b93.com accessibility score
b93.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
b93.com SEO score
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
![]()
N/A
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise B93.com 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 English. Our system also found out that B93.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.
b93.com
Open Graph data is detected on the main page of B 93. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: