6.3 sec in total
66 ms
3.7 sec
2.5 sec
Visit portlandtribune.com now to see the best up-to-date Portlandtribune content for United States and also check out these interesting facts you probably never knew about portlandtribune.com
Visit portlandtribune.comWe analyzed Portlandtribune.com page load time and found that the first response time was 66 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
portlandtribune.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value10.3 s
0/100
25%
Value9.7 s
10/100
10%
Value4,870 ms
0/100
30%
Value0.138
79/100
15%
Value27.9 s
0/100
10%
66 ms
218 ms
98 ms
109 ms
105 ms
Our browser made a total of 168 requests to load all elements on the main page. We found that 7% of them (11 requests) were addressed to the original Portlandtribune.com, 45% (76 requests) were made to Bloximages.chicago2.vip.townnews.com and 6% (10 requests) were made to Portlandtribune.friends2follow.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Api.segment.io.
Page size can be reduced by 677.2 kB (20%)
3.4 MB
2.7 MB
In fact, the total size of Portlandtribune.com main page is 3.4 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 1.7 MB which makes up the majority of the site volume.
Potential reduce by 555.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 80.6 kB, which is 13% 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 555.2 kB or 90% of the original size.
Potential reduce by 15.2 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. Portlandtribune images are well optimized though.
Potential reduce by 93.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 12.8 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. Portlandtribune.com needs all CSS files to be minified and compressed as it can save up to 12.8 kB or 17% of the original size.
Number of requests can be reduced by 72 (46%)
155
83
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portlandtribune. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
portlandtribune.com
66 ms
www.portlandtribune.com
218 ms
bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css
98 ms
layout.5bce7eb56c23d79d6ab89ab093c281ea.css
109 ms
theme-basic.a7351649a9c39f0af7c6d288a87ef140.css
105 ms
css2
93 ms
tntslider.61e562ee97efb10698d15f5cee4962dc.css
97 ms
access.d7adebba498598b0ec2c.js
91 ms
jquery.min.d6d18fcf88750a16d256e72626e676a6.js
122 ms
user.js
141 ms
bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js
106 ms
common.08a61544f369cc43bf02e71b2d10d49f.js
147 ms
tnt.ee95c0b6f1daceb31bf5ef84353968c6.js
136 ms
application.3c64d611e594b45dd35b935162e79d85.js
147 ms
polyfill.min.js
1064 ms
user-controls.578df3df79d812af55ab13bae47f9857.js
146 ms
tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js
145 ms
gpt.js
169 ms
tntslider.7177a362b66d47f546bd877a7efd6bd4.js
144 ms
tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js
144 ms
tracking.js
146 ms
fontawesome.568f3d1ab17b33ce05854081baadadac.js
155 ms
chartbeat_mab.js
91 ms
osano.js
350 ms
tracker.js
158 ms
evvnt_discovery_plugin-latest.min.js
77 ms
p.js
71 ms
up_loader.1.1.0.js
73 ms
tnt.ads.core.ee10a41bfea60001b9edb7ab35e5c9e1.js
104 ms
gtm.js
54 ms
analytics.js
16 ms
gtm.js
62 ms
gtm.js
28 ms
publisher:getClientId
129 ms
destination
44 ms
gtm.js
113 ms
collect
111 ms
collect
150 ms
collect
107 ms
js
47 ms
apstag.js
118 ms
chartbeat.js
72 ms
subscriptions.js
73 ms
32b072da-517b-11ed-8535-9f4c9e244ced.png
108 ms
39101770-517b-11ed-8535-cfdb6402c0d1.png
204 ms
240722a6-517b-11ed-8535-8b6e4edce30f.png
103 ms
6384301b6f107.image.jpg
104 ms
663526647a81e.image.jpg
106 ms
6636ea36663f5.image.jpg
102 ms
6636aaab1b1d8.image.jpg
202 ms
66366bc783004.image.jpg
201 ms
65fe70dc7b7d6.image.jpg
202 ms
6633c0aaf0519.image.jpg
200 ms
6634e80e5f961.image.jpg
202 ms
663516eb073c9.image.jpg
210 ms
663508c38cbac.image.jpg
206 ms
663503fa3858b.image.jpg
207 ms
66311f9ea991a.image.jpg
206 ms
6633c26484923.image.jpg
205 ms
639935c07c6c5.image.jpg
205 ms
6633dbcf3964c.image.jpg
250 ms
66104e9ad3f5e.image.jpg
250 ms
66343775778fc.image.jpg
251 ms
662a9919d641a.image.jpg
249 ms
66280d9f0d891.image.jpg
248 ms
6636ef2b8f20b.image.jpg
249 ms
66175fb218c5a.image.jpg
309 ms
6629dee2af818.image.jpg
252 ms
663416e3beb4d.image.jpg
254 ms
6529c0422504a.image.jpg
255 ms
66312617edda4.image.jpg
255 ms
66313d85a6101.image.jpg
251 ms
6626ab55994fb.image.jpg
308 ms
6622a03c44fc3.image.jpg
308 ms
66229ff380451.image.jpg
349 ms
66201272d5044.image.png
349 ms
660dd155809fe.image.png
446 ms
65fa472649b42.image.png
445 ms
65f8bb64f0d25.image.png
446 ms
pubads_impl.js
50 ms
tracker.gif
139 ms
analytics.min.js
138 ms
65d54549cae15.image.png
252 ms
65d544e138bbc.image.png
356 ms
65d5439c70283.image.png
357 ms
65a833adccbb7.image.png
349 ms
va9E4kDNxMZdWfMOD5VfkA.ttf
150 ms
va9B4kDNxMZdWfMOD5VnZKvuQQ.ttf
209 ms
va9B4kDNxMZdWfMOD5VnPKruQQ.ttf
248 ms
va9B4kDNxMZdWfMOD5VnSKzuQQ.ttf
249 ms
va9B4kDNxMZdWfMOD5VnLK3uQQ.ttf
250 ms
va9B4kDNxMZdWfMOD5VnFK_uQQ.ttf
249 ms
6581e376079c9.image.png
356 ms
6573acd8165c6.image.png
256 ms
657385970f767.image.png
254 ms
656505722a21a.image.png
256 ms
6552746c53595.image.png
265 ms
6540228a5e73c.image.png
257 ms
652eb15ba1bfb.image.png
260 ms
652840e65db7a.image.png
256 ms
651c3c5ed6c9a.image.png
258 ms
651c3a70de845.image.png
255 ms
6508d3ffdcbd2.image.png
258 ms
64e3bd8bee342.image.png
254 ms
64e3ab28203b4.image.png
257 ms
132916964
235 ms
662c830a2e711.image.jpg
217 ms
6625a08bc7a8f.image.jpg
219 ms
660ed528efd73.image.jpg
218 ms
66078a81c2993.image.jpg
217 ms
641cda60a71ab.preview.jpg
216 ms
644816023a9b5.image.jpg
219 ms
2d1d0752-517b-11ed-8535-3333f9778127.png
215 ms
28ced55e-517b-11ed-8535-a320d1d487c9.jpg
215 ms
settings
46 ms
rediscoveroregon.html
650 ms
47c3b4ef72a32bd09a0c06edcc70064533fd0737.html
211 ms
870.bundle.6e2976b75e60ab2b2bf8.js
10 ms
tsub-middleware.bundle.77315eced46c5ae4c052.js
56 ms
AGSKWxVXuF8mYVmjLnArl8vVNPrmQnB3ds7FcOu8MPJaa6TxtDU14VPKliM58cEM6hLE9vTWDCQ8OLCPoae4lp9zIMhk2F9jwMvyJY7AlanVJmLuWl_l6-vV2UkBDNV4giMb2HV54Cj6VA==
87 ms
uid2SecureSignal.js
285 ms
esp.js
448 ms
publishertag.ids.js
355 ms
esp.js
364 ms
encrypted-tag-g.js
543 ms
sync.min.js
547 ms
pubcid.min.js
544 ms
ob.js
569 ms
js
298 ms
html5_main-00611fcc34.js
336 ms
main-c0ce5439e8.css
432 ms
0
480 ms
m
1409 ms
263666
391 ms
p.xad.com
394 ms
370 ms
p.js
154 ms
mab
226 ms
ping
223 ms
oregon.png
122 ms
roku.png
74 ms
fire.png
74 ms
apple.png
74 ms
friends2follow_socialstack.min.css
23 ms
css
33 ms
jquery.min.js
26 ms
friends2follow_tracking.min.js
104 ms
friends2follow_antifraud.min.js
38 ms
friends2follow_socialstack.min.js
25 ms
map
954 ms
Portland%20Tribune_H_4c_0.jpg
18 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
6 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
8 ms
social.woff
6 ms
1f3c6.png
787 ms
friends2follow_socialstack_on_init.min.js
716 ms
1f3d3.png
747 ms
1f609.png
752 ms
1fae3.png
837 ms
1f5e3.png
931 ms
1f399.png
752 ms
f2fi.php
75 ms
jquery.f2f.cycle2.min.js
21 ms
glyphicons-halflings-regular.woff
11 ms
friends2follow_infinitescroll.min.js
5 ms
tg.php
35 ms
show_companion_ad.js
37 ms
AGSKWxVD26iQCIhqpbDJ9k_bUa-y6qFw1lLPKvkV1DiPWDJUYhuWEJ5IOkjqtB7YZIs0Uw5o6nONwzkXA0WSTFgj4tckrZyjeSDXa3RgQTbf1086bTFEkgSJjngGQUcNYoTd7mhTiy-5iQ==
47 ms
portlandtribune.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
portlandtribune.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 Portlandtribune.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 Portlandtribune.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.
portlandtribune.com
Open Graph description is not detected on the main page of Portlandtribune. 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: