2.2 sec in total
76 ms
1.6 sec
548 ms
Click here to check amazing Hearphilly content. Otherwise, check out these important facts you probably never knew about hearphilly.com
Audacy brings people together around what moves them, and helps advertisers connect to those audiences. We engage over 170 MM consumers each month across our connected platforms.
Visit hearphilly.comWe analyzed Hearphilly.com page load time and found that the first response time was 76 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
hearphilly.com performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value11.1 s
0/100
25%
Value12.3 s
3/100
10%
Value4,250 ms
1/100
30%
Value0.468
19/100
15%
Value27.1 s
0/100
10%
76 ms
106 ms
47 ms
51 ms
59 ms
Our browser made a total of 183 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hearphilly.com, 50% (92 requests) were made to Visitphilly.com and 13% (24 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (661 ms) relates to the external source Scontent.cdninstagram.com.
Page size can be reduced by 1.4 MB (67%)
2.2 MB
708.8 kB
In fact, the total size of Hearphilly.com main page is 2.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 95.4 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. This page needs HTML code to be minified as it can gain 16.9 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 95.4 kB or 82% of the original size.
Potential reduce by 24.1 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. Hearphilly images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 73% of the original size.
Potential reduce by 318.1 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. Hearphilly.com needs all CSS files to be minified and compressed as it can save up to 318.1 kB or 85% of the original size.
Number of requests can be reduced by 108 (63%)
172
64
The browser has sent 172 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hearphilly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
hearphilly.com
76 ms
hearphilly
106 ms
hearphilly
47 ms
51 ms
core.js
59 ms
simpledetect.js
57 ms
font-awesome.min.css
8 ms
museo.css
67 ms
cardo.css
68 ms
opensans-google.css
55 ms
screen.css
76 ms
enhanced.css
93 ms
responsive.css
102 ms
screen-custom.css
72 ms
hearphilly.css
91 ms
brand
16 ms
launchPlayer.js
197 ms
search_widget.js.php
224 ms
jquery-2.1.4.min.js
146 ms
jquery.core.min.js
180 ms
jquery.cycle2.js
114 ms
jquery.panzoom.js
125 ms
jquery.trailbox.js
90 ms
jquery.sidr.js
90 ms
jquery.nicescroll.js
179 ms
jquery.event.move.js
112 ms
jquery.twentytwenty.js
111 ms
idangerous.swiper.js
198 ms
idangerous.swiper.scrollbar.js
128 ms
jquery-ui.min.js
284 ms
mobiscroll.custom-2.9.2.min.js
129 ms
jquery.autocomplete.js
167 ms
jquery.autocomplete.init.js
150 ms
searchbyname.js
151 ms
functions.js
195 ms
responsive.js
195 ms
newsform.js
194 ms
google_tracking.js
197 ms
gevent_tracking.js
209 ms
additional_tracking.js
212 ms
adrotator.js
213 ms
mmConversionTagVU.js
215 ms
optinmonster.js
216 ms
varnish-refresh.js
269 ms
flip.min.js
269 ms
brand
51 ms
jScrollPane.css
270 ms
jquery.scrollTo-min.js
233 ms
dc.js
39 ms
jquery.easing.js
224 ms
jquery.jplayer.min.js
251 ms
jScrollPane.js
232 ms
hearplayers.js
231 ms
lb
12 ms
nav-red-triangle.png
94 ms
1661714_1267570579928463_117025891_n.jpg
354 ms
bg-content.gif
179 ms
m-logo.png
179 ms
nethead.png
196 ms
netheadsep.png
198 ms
social.png
199 ms
m-button.png
200 ms
12822526_453395038203144_1150522197_n.jpg
550 ms
12826273_1775502886003984_1309394552_n.jpg
661 ms
bg-header-wrap.gif
201 ms
logo-print.png
216 ms
home-visit-philadelphia2.png
308 ms
search-icon.gif
307 ms
search.gif
297 ms
marker-county-nav.gif
289 ms
bg-main-nav-drop.png
288 ms
CityHallTowerView_M.Fischetti002-400VP.jpg
268 ms
pats-cheesesteaks-philadelphia-600vp-icon.jpg
273 ms
like.php
127 ms
CityHallTowerView_M.Fischetti002-400VP.jpg
260 ms
visitphilly-overnight-hotel-package-square-600vp.jpg
249 ms
bg-main-nav-drop-alt.png
232 ms
visitphilly-overnight-hotel-package-square-600vp.jpg
230 ms
ManayunkArtsFestival_J.Fusco079-400vp.jpg
260 ms
bg-landing-main-top.png
261 ms
hear-philly-logo.gif
259 ms
pat.gif
246 ms
spacer.gif
242 ms
choose.gif
241 ms
with-love-336x280.jpg
439 ms
listen.gif
397 ms
cal.png
227 ms
analytics.js
40 ms
search.png
33 ms
bg.jpg
77 ms
museosans-100-webfont.woff
341 ms
museosans_700-webfont.woff
339 ms
playerback.gif
343 ms
jp.png
342 ms
slash.gif
383 ms
ps
34 ms
qeKvIRsJabD.js
388 ms
LVx-xkvaJ0b.png
401 ms
ituneso.gif
375 ms
lbtn.png
374 ms
lbtna.png
374 ms
collect
122 ms
collect
121 ms
pixel
118 ms
111 ms
setuid
114 ms
Pug
138 ms
icon-facebok-like.gif
336 ms
foodspot.png
357 ms
bg-footer.gif
354 ms
marker-dossier.gif
352 ms
visit-philadelphia-logo-white.png
356 ms
UWISHUNU-logo-white.png
356 ms
city-logo-white.png
356 ms
PA-logo-white.png
365 ms
discover-usa-white.png
341 ms
fontawesome-webfont.woff
69 ms
collect
248 ms
museosans-300-webfont.woff
272 ms
museosans_900-webfont.woff
272 ms
museosans_500-webfont.woff
273 ms
Pix-1x1.gif
39 ms
tap.php
37 ms
demconf.jpg
38 ms
39 ms
pixel
34 ms
quant.js
165 ms
likebox.php
201 ms
cmap
201 ms
api.min.js
195 ms
async_survey
222 ms
fbds.js
218 ms
__utm.gif
49 ms
__utm.gif
56 ms
circle-loader.gif
79 ms
sd
54 ms
3463.js
36 ms
pixel;r=1836344464;a=p-3a3nTUOb22a-w;fpan=1;fpa=P0-833118028-1458283772795;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458283772795;tzo=-180;ref=;url=http%3A%2F%2Fwww.visitphilly.com%2Fhear-philly%2F;ogl=site_name.Philadelphia%20-%20Official%20Visitor%20Site%20-%20visitphilly%252Ecom%2Ctype.article%2Curl.http%3A%2F%2Fwww%252Evisitphilly%252Ecom%2Fhear-philly%2F
41 ms
hDvwL1_H7g-.css
63 ms
56WNbrUYLbL.css
117 ms
xxJgcoj8mOR.css
129 ms
GN27K_co9Wc.css
145 ms
q68gy-v_YMF.js
202 ms
FJmpeSpHpjS.js
234 ms
0wM5s1Khldu.js
144 ms
1bNoFZUdlYZ.js
140 ms
OloiM1PZafe.js
143 ms
LTv6ZK-5zxz.js
261 ms
1FCa-btixu2.js
257 ms
Oagsvfb4VWi.js
254 ms
pObvZSrFc_4.js
256 ms
HgJbVwzBr8E.js
252 ms
H3EKDTObx05.js
256 ms
OZFAYTv-ZUg.js
257 ms
jquery.min.js
39 ms
82 ms
prompt_embed_static.js
92 ms
print.css
63 ms
944958_10154011396269050_965766867740867360_n.jpg
121 ms
539973_10150794295934050_1382001764_n.jpg
137 ms
11822810_10207288008019764_5605772411186257005_n.jpg
155 ms
12734081_10205629760411852_7692067259109303169_n.jpg
171 ms
1930441_185441805169009_407264863762493360_n.jpg
172 ms
10151203_902299759867703_4398524085874960210_n.jpg
175 ms
12832484_557079207796519_8491901182534516924_n.jpg
173 ms
12734117_10201365556096924_5810469888300220075_n.jpg
175 ms
12376293_842209702558394_3559598383171262404_n.jpg
172 ms
HEyyDkPknAC.png
96 ms
wL6VQj7Ab77.png
96 ms
s7jcwEQH7Sx.png
94 ms
gxbPuQdXIZP.png
22 ms
I6-MnjEovm5.js
38 ms
pQrUxxo5oQp.js
39 ms
nr-885.min.js
42 ms
s
86 ms
200044
27 ms
208045
23 ms
208631
18 ms
10 ms
u
53 ms
353bb08bf8
64 ms
webfont.js
4 ms
cf63dd252e3d1438205365-subscribe-notext.jpg
31 ms
hearphilly.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
hearphilly.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
hearphilly.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
Image elements do not have [alt] attributes
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 Hearphilly.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 Hearphilly.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.
hearphilly.com
Open Graph description is not detected on the main page of Hearphilly. 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: