2 sec in total
31 ms
1.2 sec
732 ms
Welcome to wogl.com homepage info - get ready to check WOGL best content right away, or after learning these important things about wogl.com
Philly's #1 station for classic hits and a home of the 70s, 80s, and 90s! Tune in and listen to Big 98.1 with any device on the Audacy app.
Visit wogl.comWe analyzed Wogl.com page load time and found that the first response time was 31 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
wogl.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value16.9 s
0/100
25%
Value13.0 s
2/100
10%
Value9,250 ms
0/100
30%
Value0.134
80/100
15%
Value37.6 s
0/100
10%
31 ms
47 ms
37 ms
34 ms
57 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Wogl.com, 42% (20 requests) were made to Images.radio.com and 29% (14 requests) were made to Audacy.com. The less responsive or slowest element that took the longest time to load (691 ms) relates to the external source Images.radio.com.
Page size can be reduced by 528.2 kB (44%)
1.2 MB
681.3 kB
In fact, the total size of Wogl.com main page is 1.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. 60% of websites need less resources to load. HTML takes 589.8 kB which makes up the majority of the site volume.
Potential reduce by 462.8 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 462.8 kB or 78% of the original size.
Potential reduce by 1.3 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. WOGL images are well optimized though.
Potential reduce by 64.2 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 64.2 kB or 17% of the original size.
Number of requests can be reduced by 14 (37%)
38
24
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WOGL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
wogl.com
31 ms
wogl.com
47 ms
big981
37 ms
polyfills.js
34 ms
loadAmazonAps.js
57 ms
187177-100482611063863.js
586 ms
gpt.js
586 ms
sfp.js
447 ms
pub.js
689 ms
tag.js
585 ms
2001290.js
117 ms
flipptag.js
443 ms
branch-2.49.0.min.js
116 ms
app.531676be.js
89 ms
chunk-vendors.1703b912.js
439 ms
components.css
89 ms
components.js
434 ms
apstag.js
632 ms
WOGLFMUnityLogo-83d69b6b-1393-452e-a4dd-b10d63cd1bd0.png
691 ms
image.jpg
606 ms
271A2485335B432CAD907E53BA8A1D5C-88be847b-6d81-4076-aa8b-f0c0c5ff6153.png
670 ms
Captain-Hirams-River-Front-Rooms7-1-960237ba-fa39-462f-8d1e-1841042bc8f2.jpg
494 ms
GettyImages1148365563-c2a83521-7930-4485-a961-d6046b2973cf.jpg
457 ms
GettyImages1047316906-1-4b4d281a-49c9-4a49-86a9-9e480ae31837.jpg
483 ms
GettyImages2032411647-21f16296-52d5-4413-8c8f-b993590cd77b.jpg
438 ms
ByrneParamoreGetty-7e496210-b056-4843-ae97-5281175d5c0d.jpg
438 ms
SeaHearNowJoeCingranaAudacy-6dba8bed-d035-4369-b456-f427824a46dc.jpg
439 ms
WOGLFM_CoopShowReplay_Logo.jpeg
451 ms
d166e2523f.jpg
475 ms
48337d87b9.jpg
452 ms
GettyImages1354771544-1a9cd1cb-30f7-45bb-8d9b-87446e2b0e82.jpg
453 ms
GettyImages1297492649-cdd91059-e4a5-4342-a8ab-ec0903cc228c.jpg
467 ms
JasonKelce-2-673dd808-8b2c-4362-b4c1-065a1d6931cb.jpg
573 ms
JasonKelce-1-09eb958c-b9e1-4837-ba81-a25233b29c5c.jpg
609 ms
RitchieKelce-397db837-e80f-486a-a21f-d24f42c51c01.jpg
542 ms
USATSI22047847-d5b6dd2e-e8ca-4fd4-9520-8bc144988077.jpg
556 ms
GettyImages2058809072-346e2c9d-68eb-4f01-9f8d-2ac1c6bf4966.jpg
682 ms
JasonKelce-1d706328-3238-44b9-86b1-1a4810de57c7.jpg
562 ms
BlakeSnell-2623e55e-7c3c-43fe-97be-c857f35f9ae0.jpg
691 ms
GettyImages664648470-edc150d5-fc76-45fe-b7e8-3550ec34ced2.jpg
599 ms
MaisonNeueExtendedWEB-Book.woff
92 ms
MaisonNeueExtendedWEB-Demi.woff
90 ms
MaisonNeueExtendedWEB-Bold.woff
90 ms
circularstd-medium.woff
109 ms
MaisonNeueExtendedWEB-Medium.woff
89 ms
MaisonNeueWEB-Book.woff
89 ms
MaisonNeueExtendedWEB-ExtraBold.woff
160 ms
pubads_impl.js
158 ms
wogl.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
wogl.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
Missing source maps for large first-party JavaScript
wogl.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wogl.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 Wogl.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.
wogl.com
Open Graph data is detected on the main page of WOGL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: