1.8 sec in total
637 ms
1.1 sec
70 ms
Visit 970espn.com now to see the best up-to-date 970 Espn content for United States and also check out these interesting facts you probably never knew about 970espn.com
Pittsburgh Sports Hub is for all things Pittsburgh Sports Related.
Visit 970espn.comWe analyzed 970espn.com page load time and found that the first response time was 637 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.
970espn.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value5.4 s
20/100
25%
Value8.0 s
21/100
10%
Value5,600 ms
0/100
30%
Value0.002
100/100
15%
Value17.5 s
4/100
10%
637 ms
67 ms
75 ms
71 ms
73 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 970espn.com, 5% (3 requests) were made to I.iheart.com and 3% (2 requests) were made to Z.moatads.com. The less responsive or slowest element that took the longest time to load (637 ms) relates to the external source Foxsportspgh.iheart.com.
Page size can be reduced by 1.2 MB (59%)
2.1 MB
863.7 kB
In fact, the total size of 970espn.com main page is 2.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. HTML takes 1.3 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 81% of the original size.
Potential reduce by 1.0 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. 970 Espn images are well optimized though.
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 3.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. 970espn.com needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 11% of the original size.
Number of requests can be reduced by 51 (86%)
59
8
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 970 Espn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
foxsportspgh.iheart.com
637 ms
bundle.8b37dfa4e56540828535.css
67 ms
local.bc06f128f534d4a5d747.css
75 ms
core-components-tiles-OnairTileLoader-component.12f62d6d6ad5771d626e.css
71 ms
core-page-blocks-datasource-DatasourceLoader-component.ed118ca85e0cefc658b6.css
73 ms
Datasource-component.a1eb25fbdc158e499608.css
75 ms
Grid-component.9e05f3f8fa0e6b993347.css
76 ms
components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css
77 ms
TrafficTile-component.79b6ef8f3442074e2437.css
77 ms
LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css
79 ms
Heading-component.d79a5c95e6ef67a97bca.css
84 ms
Show-component.608ec1ff0656c8b676a1.css
81 ms
core-page-blocks-datasource-DatasourceTileLoader-component.a1eb25fbdc158e499608.css
82 ms
FauxButton-component.1f25bb623660eb4f88c1.css
77 ms
Eyebrow-component.23e83d8b8cab22ea99d6.css
82 ms
AptivadaKeywordContest-component.a21f13419d9d48bf409a.css
84 ms
Podcasts-component.570accd833088f4c4e7d.css
85 ms
ImageTile-component.c2cbd469fbc0bd11cbdf.css
87 ms
Card-component.c66d212af09897afcdd6.css
88 ms
WeatherTile-component.ca557d80a0c5075ed0c1.css
86 ms
sdk.js
70 ms
moatheader.js
80 ms
ebx.js
215 ms
runtime.214e6c876f50b2a8a6a2.js
139 ms
vendor.82993fc136b73cc6a6f2.js
142 ms
bundle.60f9f8edb929059ddf6f.js
195 ms
packages-renderer-shared-ui-src-elements-MagicLink-component.748e878b4b4ef9b70e33.js
138 ms
src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_HeaderSearch_component_tsx-src_-b801d3.ebb7c95d698279b1c9ec.js
139 ms
local.a5b480bb028a49b07c6c.js
139 ms
core-components-tiles-OnairTileLoader-component.3c9c776801ce3f5ccf05.js
145 ms
core-page-blocks-datasource-DatasourceLoader-component.be189e440f36a30fac9f.js
139 ms
packages_renderer_shared_core_src_lib_ads_ts.1c411bb05fe7a8d6fb44.js
141 ms
Datasource-component.09c541938624ea67842c.js
138 ms
Grid-component.48dae21730bceb9ee5e7.js
140 ms
ContentFeedItem-component.2c07f0e7be984e8aee02.js
143 ms
components-tiles-ContentTile-component.22ddd6a7b1c8a1bc4e2d.js
140 ms
LeadFeedItem-component.4330af319e52f7557387.js
141 ms
core-components-tiles-WeatherTileLoader-component.3076f6660778382f42b1.js
141 ms
TrafficTile-component.01dffae824fc382d134e.js
143 ms
LoadMoreFromCursor-component.dd840a1844d3d6bb0d7d.js
143 ms
ShowCollection-component.0c3f9b3068fe83748412.js
105 ms
Heading-component.ea88c81b8d34c977158c.js
148 ms
Show-component.cdfd0315af774eaef8dd.js
138 ms
core-page-blocks-podcast-PodcastsLoader-component.71edb632222c77f48f93.js
136 ms
core-page-blocks-datasource-DatasourceTileLoader-component.70fbc1958e35a8aed3b5.js
136 ms
FauxButton-component.6f17f4f82d52801c5c49.js
137 ms
core-page-blocks-contest-KeywordContestLoader-component.eb063dc982e7b1285f9b.js
135 ms
Eyebrow-component.533482f1ba2c4fcd4202.js
135 ms
AptivadaKeywordContest-component.b7ea73f8063fca6968f6.js
137 ms
vendors-node_modules_pnpm_isomorphic-dompurify_0_23_0_node_modules_isomorphic-dompurify_browser_js.6c4667c6ebbb3bd5aea7.js
132 ms
Podcasts-component.c822825f35d41178cdf7.js
131 ms
ImageTile-component.b3ff14a77346457b64fe.js
133 ms
Card-component.24dee8840408569eb2c3.js
133 ms
WeatherTile-component.e8e44d3a690efdf646b4.js
133 ms
659586999075608a8f771efd
162 ms
f79fc341-a979-4863-81b0-eea1ddc6e07b
94 ms
627ed0263f19c6325b37ec16
109 ms
v2
81 ms
n.js
91 ms
iframe.html
30 ms
970espn.com accessibility score
970espn.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
Page has valid source maps
970espn.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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 970espn.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 970espn.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.
970espn.com
Open Graph data is detected on the main page of 970 Espn. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: