2.8 sec in total
148 ms
2 sec
619 ms
Welcome to z100portland.com homepage info - get ready to check Z100 Portland best content for United States right away, or after learning these important things about z100portland.com
Portland's #1 Hit Music Station, Z100
Visit z100portland.comWe analyzed Z100portland.com page load time and found that the first response time was 148 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
z100portland.com performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value3.6 s
61/100
25%
Value10.4 s
8/100
10%
Value9,730 ms
0/100
30%
Value0.094
91/100
15%
Value22.8 s
1/100
10%
148 ms
789 ms
59 ms
25 ms
40 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Z100portland.com, 20% (30 requests) were made to Flint-img.ccrd.clearchannel.com and 17% (26 requests) were made to Content.clearchannel.com. The less responsive or slowest element that took the longest time to load (789 ms) relates to the external source Z100portland.iheart.com.
Page size can be reduced by 1.5 MB (30%)
5.1 MB
3.6 MB
In fact, the total size of Z100portland.com main page is 5.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. 85% 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. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 92.2 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 19.9 kB, which is 17% 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 92.2 kB or 79% of the original size.
Potential reduce by 84.6 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. Z100 Portland images are well optimized though.
Potential reduce by 1.1 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.1 MB or 72% of the original size.
Potential reduce by 237.6 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. Z100portland.com needs all CSS files to be minified and compressed as it can save up to 237.6 kB or 81% of the original size.
Number of requests can be reduced by 90 (60%)
150
60
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Z100 Portland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 70 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
z100portland.com
148 ms
z100portland.iheart.com
789 ms
core.css
59 ms
app.css
25 ms
ihearticons.css
40 ms
station_styles.css
37 ms
custom.modernizr.js
33 ms
jquery.js
42 ms
jquery.cookie.js
31 ms
sdk.min.js
89 ms
ads.min.js
33 ms
plusone.js
91 ms
slider.min.js
30 ms
timeline.min.js
29 ms
LAB.min.js
36 ms
main.min.js
35 ms
foundation.js
33 ms
foundation.orbit.js
37 ms
foundation.forms.js
35 ms
foundation.section.js
35 ms
foundation.reveal.js
38 ms
init.js
36 ms
challenge
168 ms
gpt.js
92 ms
analytics.js
92 ms
cb=gapi.loaded_0
84 ms
sdk.js
223 ms
thumbNew.php
197 ms
widgets.js
215 ms
cb=gapi.loaded_1
78 ms
fastbutton
89 ms
search_btn_icon_black.png
70 ms
default
69 ms
0.jpg
64 ms
7-eleven-byo-cup-day-a2bacfcf15e94a88.jpg
56 ms
social_media_icons_0_1431927301.png
159 ms
ti.js
46 ms
HTMLPoll.js
141 ms
163 ms
siteconfig.js
334 ms
studionumba_0_1445281665.png
224 ms
zlineup_0_1445281429.png
350 ms
spark-mobile-play-button-sprite-v2.png
35 ms
spark-mobile-iheartradio-logo.png
35 ms
localinfo_weather_icons.png
35 ms
localinfo_traffic_icon.png
36 ms
module-title-corner.png
35 ms
0.jpg
36 ms
0.jpg
139 ms
0.jpg
143 ms
0.jpg
127 ms
884_1396019308.png
147 ms
thumbCrop.php
147 ms
thumbCrop.php
331 ms
thumbCrop.php
123 ms
thumbCrop.php
147 ms
thumbCrop.php
140 ms
thumbCrop.php
218 ms
thumbCrop.php
144 ms
thumbCrop.php
324 ms
thumbCrop.php
147 ms
thumbCrop.php
148 ms
thumbCrop.php
215 ms
thumbNew.php
150 ms
thumbCrop.php
215 ms
thumbCrop.php
215 ms
thumbCrop.php
325 ms
thumbCrop.php
216 ms
thumbCrop.php
325 ms
thumbCrop.php
216 ms
thumbCrop.php
218 ms
thumbCrop.php
218 ms
thumbCrop.php
324 ms
884_1411507635.png
323 ms
recaptcha.js
120 ms
e2eDetect.js
114 ms
s_code.js
114 ms
cb=gapi.loaded_0
116 ms
cb=gapi.loaded_1
117 ms
p2
113 ms
pubads_impl_82.js
108 ms
collect
121 ms
postmessageRelay
234 ms
p
220 ms
bOa0NM1Her35hWadbi-bnq.js
101 ms
g6qlE9hbcrtCq0agucy03kPIdFYel5UicYHotHMXHKo.js
190 ms
bridge.min.js
180 ms
timeline_more.html
323 ms
module-title-corner.png
143 ms
cc.js
148 ms
widget.now-playing.min.js
146 ms
widget.shoutout.min.js
144 ms
dynamic-lead-nav-sprite-black.png
113 ms
PollsController.js
113 ms
container.html
72 ms
embed.html
238 ms
quickio.js
83 ms
3193398744-postmessagerelay.js
74 ms
rpc:shindig_random.js
55 ms
ads
104 ms
v2
80 ms
147 ms
refresh.png
44 ms
widget.shoutout.css
29 ms
audio.png
19 ms
text.png
28 ms
help.png
27 ms
logo.png
28 ms
cb=gapi.loaded_0
5 ms
dpx
8 ms
ads
49 ms
37685246
10 ms
5 ms
reload
66 ms
1020265
53 ms
29589909
49 ms
31477952
53 ms
s79154530249070
49 ms
xrefid.xgi
45 ms
ads
48 ms
DARTfooterNewSplit.js
32 ms
DFPheader.js
121 ms
json2.js
103 ms
jquery.min.js
86 ms
jquery.cookie.js
103 ms
HTMLPlayer.js
138 ms
FlashPlayer.js
103 ms
EmbedPlayer.js
102 ms
SharePanelManager.js
167 ms
LayoutManager.js
166 ms
MediaManager.js
203 ms
PreRollManager.js
167 ms
GlobalDataObj.js
201 ms
TrackingObject.js
201 ms
WidgetModeView.js
204 ms
ima3.js
56 ms
image
51 ms
3272652718788357245
39 ms
moatad.js
87 ms
osd.js
20 ms
ads
103 ms
52154.gif
28 ms
s_code-secure.js
107 ms
MPI_300x250_Q10027_GM_MU_Spectrum_iHeart_ST.jpg
75 ms
image
124 ms
sbhK2lTE.js
73 ms
pixel.gif
57 ms
beacon.js
140 ms
swfobject.js
69 ms
cTrvNaRi.html
12 ms
pixel.gif
5 ms
15991
25 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
26 ms
z100portland.com accessibility score
z100portland.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
Page has valid source maps
z100portland.com SEO score
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 Z100portland.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 Z100portland.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.
z100portland.com
Open Graph data is detected on the main page of Z100 Portland. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: