1.9 sec in total
728 ms
1.1 sec
60 ms
Visit weli.com now to see the best up-to-date WELI content and also check out these interesting facts you probably never knew about weli.com
960 WELI is New Haven's News, Weather and Traffic station and features Vinnie Penn in the morning. 960 WELI is an iHeartRadio station in New Haven, Connecticut.
Visit weli.comWe analyzed Weli.com page load time and found that the first response time was 728 ms and then it took 1.1 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.
weli.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.4 s
39/100
25%
Value8.3 s
19/100
10%
Value3,620 ms
1/100
30%
Value0.002
100/100
15%
Value16.0 s
6/100
10%
728 ms
78 ms
77 ms
76 ms
77 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 Weli.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 (728 ms) relates to the external source 960weli.iheart.com.
Page size can be reduced by 1.2 MB (56%)
2.1 MB
936.0 kB
In fact, the total size of Weli.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 79% of the original size.
Potential reduce by 1.8 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. WELI images are well optimized though.
Potential reduce by 181.6 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 181.6 kB or 24% 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. Weli.com has all CSS files already compressed.
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 WELI. 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.
960weli.iheart.com
728 ms
bundle.af116c1d41aebd831d9c.css
78 ms
local.bc06f128f534d4a5d747.css
77 ms
core-components-tiles-OnairTileLoader-component.12f62d6d6ad5771d626e.css
76 ms
core-page-blocks-datasource-DatasourceLoader-component.ed118ca85e0cefc658b6.css
77 ms
Datasource-component.a1eb25fbdc158e499608.css
83 ms
Grid-component.9e05f3f8fa0e6b993347.css
83 ms
components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css
85 ms
TrafficTile-component.79b6ef8f3442074e2437.css
85 ms
Heading-component.d79a5c95e6ef67a97bca.css
84 ms
LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css
91 ms
Show-component.608ec1ff0656c8b676a1.css
87 ms
core-page-blocks-datasource-DatasourceTileLoader-component.a1eb25fbdc158e499608.css
88 ms
FauxButton-component.1f25bb623660eb4f88c1.css
85 ms
AptivadaKeywordContest-component.a21f13419d9d48bf409a.css
88 ms
Eyebrow-component.23e83d8b8cab22ea99d6.css
88 ms
Podcasts-component.570accd833088f4c4e7d.css
90 ms
ImageTile-component.c2cbd469fbc0bd11cbdf.css
95 ms
Card-component.c66d212af09897afcdd6.css
92 ms
WeatherTile-component.ca557d80a0c5075ed0c1.css
94 ms
sdk.js
171 ms
moatheader.js
89 ms
ebx.js
169 ms
runtime.cb66cc5e8cd4543b7929.js
153 ms
vendor.63f2f7bffa688d9d9622.js
153 ms
bundle.2a3672ad9e244a3e76ed.js
238 ms
packages-renderer-shared-ui-src-elements-MagicLink-component.61532071211bf452d2ef.js
155 ms
src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_HeaderSearch_component_tsx-src_-b801d3.6041e11b8d0e121e52b7.js
226 ms
local.66ed3ba7b565dcbed23f.js
155 ms
core-components-tiles-OnairTileLoader-component.22fd96ce3a97461201e5.js
222 ms
core-page-blocks-datasource-DatasourceLoader-component.f48ec165e3da9a949f55.js
226 ms
packages_renderer_shared_core_src_lib_ads_ts.b42bd2acb8a91fae3845.js
223 ms
Datasource-component.1423c7d635806130822c.js
229 ms
Grid-component.48dae21730bceb9ee5e7.js
226 ms
ContentFeedItem-component.a58f9b17ed1802cd6512.js
229 ms
components-tiles-ContentTile-component.8fe9a91f6ecd8ec889d2.js
230 ms
LeadFeedItem-component.f9b025ed7a795a039e16.js
228 ms
core-components-tiles-WeatherTileLoader-component.224b5c1493848aa4f0f6.js
232 ms
TrafficTile-component.47ac314dfe91b6ebc04f.js
231 ms
Heading-component.ea88c81b8d34c977158c.js
235 ms
LoadMoreFromCursor-component.bb890d9dab9374f42e37.js
183 ms
core-page-blocks-podcast-PodcastsLoader-component.c847d80e9aa862b03d51.js
183 ms
ShowCollection-component.9692637de0ea45061f03.js
182 ms
Show-component.20f0fd63ed9d624ed268.js
181 ms
core-page-blocks-datasource-DatasourceTileLoader-component.05d77890dc9884cc76e2.js
182 ms
FauxButton-component.6f17f4f82d52801c5c49.js
180 ms
core-page-blocks-contest-KeywordContestLoader-component.5e0cc4120d526a5ea860.js
178 ms
AptivadaKeywordContest-component.d932ebf2afeb78ef5324.js
182 ms
Eyebrow-component.533482f1ba2c4fcd4202.js
178 ms
vendors-node_modules_pnpm_isomorphic-dompurify_0_27_0_node_modules_isomorphic-dompurify_browser_js.05cdd4f29edec5e3d7e3.js
178 ms
Podcasts-component.ab2989f0ebc0ae9ef4c1.js
179 ms
ImageTile-component.b3ff14a77346457b64fe.js
180 ms
Card-component.24dee8840408569eb2c3.js
177 ms
WeatherTile-component.e8eb1af90b1d00d39f16.js
218 ms
60cb5a9a9eec8ff06d98ad80
233 ms
f79fc341-a979-4863-81b0-eea1ddc6e07b
157 ms
627ed0263f19c6325b37ec16
161 ms
v2
73 ms
n.js
59 ms
iframe.html
33 ms
weli.com accessibility score
weli.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
Issues were logged in the Issues panel in Chrome Devtools
weli.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 Weli.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 Weli.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.
weli.com
Open Graph data is detected on the main page of WELI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: