3.4 sec in total
233 ms
2.9 sec
187 ms
Click here to check amazing Pdx content for United States. Otherwise, check out these important facts you probably never knew about pdx.com
Portland International Airport
Visit pdx.comWe analyzed Pdx.com page load time and found that the first response time was 233 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
pdx.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value16.0 s
0/100
25%
Value9.5 s
11/100
10%
Value770 ms
38/100
30%
Value0.534
14/100
15%
Value16.1 s
6/100
10%
233 ms
1007 ms
404 ms
169 ms
323 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 33% of them (41 requests) were addressed to the original Pdx.com, 16% (20 requests) were made to Static.xx.fbcdn.net and 15% (19 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Pdx.com.
Page size can be reduced by 233.8 kB (18%)
1.3 MB
1.1 MB
In fact, the total size of Pdx.com main page is 1.3 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 58.3 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 13.8 kB, which is 20% 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 58.3 kB or 84% of the original size.
Potential reduce by 124.0 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. Obviously, Pdx needs image optimization as it can save up to 124.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 39.8 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 39.8 kB or 35% of the original size.
Potential reduce by 11.7 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. Pdx.com needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 82% of the original size.
Number of requests can be reduced by 47 (39%)
121
74
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pdx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
pdx.com
233 ms
PDX
1007 ms
PublicSite
404 ms
theme-airports
169 ms
theme
323 ms
datetime-picker
167 ms
jquery
414 ms
PublicSite
123 ms
jqueryUI-Blue
463 ms
datetime-picker
329 ms
cycle2
204 ms
parking
287 ms
PopUtility.js
299 ms
jsapi
36 ms
333 ms
PortLogo.png
74 ms
pdx_home_img01.jpg
201 ms
PDX_Home_QkLnk_Arrivals_Icon.gif
120 ms
PDX_Home_QkLnk_ShpsRstrnts_Icon.gif
121 ms
PDX_Home_QkLnk_Parking_Icon.gif
120 ms
PDX_Home_Ftr_NnstpDstntns.jpg
195 ms
PDX_Home_Ftr_PaytoPark.jpg
473 ms
PDX_Home_Ftr_GldKeyVlt.jpg
194 ms
PDX_Home_Ftr_CrbnOffsets.jpg
194 ms
PDX_WhatsNew_SpringFling.jpg
235 ms
PDX_WhatsNew_GlobalEntry.jpg
195 ms
PDX_home_WhatsNew_PDXNext.jpg
205 ms
PDX_WhatsNew_JobsPDX.jpg
195 ms
PDX_WhatsNew_75thTimeline.jpg
205 ms
PDX_Home_WeatherIcon.gif
232 ms
PDX_Home_TrafficIcon.gif
229 ms
PDX_Home_clock.gif
234 ms
PDX_Home_TrvlIcn.gif
235 ms
body-tile-x.jpg
88 ms
header-tile-x.jpg
89 ms
TwitterIcon.png
90 ms
FaceBookIcon.png
88 ms
InstagramIcon.png
231 ms
YouTubeIcon.png
197 ms
LinkedInIcon.png
196 ms
RSSIcon.png
197 ms
btn_airports_roll.jpg
197 ms
btn_marine.jpg
234 ms
btn_properties.jpg
269 ms
btn_inside.jpg
270 ms
lft_nav_menu_shdw.jpg
269 ms
menu_arrow.gif
268 ms
window-top-hatch.gif
400 ms
window-bottom-hatch_sml.gif
399 ms
qlink_background.gif
404 ms
open_window_hd_bg_top.gif
404 ms
window-bottom-hatch.gif
404 ms
red_arrow.gif
403 ms
likebox.php
169 ms
glyphicons-halflings-regular.woff
381 ms
widgets.js
87 ms
analytics.js
13 ms
40 ms
ebiMDO3r-8l.css
258 ms
wakJkBioHgT.css
301 ms
6qHpHChjY_J.css
358 ms
ztINr5qMqM_.css
407 ms
uVjHKJ0glvg.css
437 ms
q68gy-v_YMF.js
476 ms
FJmpeSpHpjS.js
475 ms
0wM5s1Khldu.js
400 ms
1bNoFZUdlYZ.js
397 ms
njO1TPvGzoR.js
443 ms
1QuX41zDRrx.js
444 ms
Oagsvfb4VWi.js
503 ms
LTv6ZK-5zxz.js
623 ms
1FCa-btixu2.js
526 ms
default+en.css
10 ms
default.css
16 ms
default+en.I.js
14 ms
default.css
43 ms
GetWeatherData
94 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
130 ms
ui-bg_flat_100_ffffff_40x100.png
91 ms
ui-bg_gloss-wave_100_ffffff_500x100.png
92 ms
ui-bg_highlight-hard_15_919BA4_1x100.png
93 ms
bg_top.gif
98 ms
ui-bg_highlight-hard_50_3B83CB_1x100.png
96 ms
syndication
103 ms
276384787139264513
170 ms
rkZnDSZFT7t3E4KD.jpg
15 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
142 ms
xKoMz6UO_normal.jpg
11 ms
square-logo_normal.png
8 ms
e74b07686f646b8af139987a132e4dc6_normal.jpeg
56 ms
OTkSdMvE_normal.png
104 ms
t0U-gaMK_normal.jpeg
169 ms
m9Tj9vq-_normal.jpg
181 ms
a_PnLeL0_normal.jpg
184 ms
vbv1E0B0_normal.jpeg
184 ms
ulyiw6n0_normal.jpg
182 ms
CX9vE4aUsAA5yJE.jpg:small
183 ms
Cds4zi7UMAAEffx.jpg:small
185 ms
Cdroy-zWAAAVZNp.jpg:small
186 ms
CdpimYCWEAAj1B1.jpg:small
183 ms
CdovK2UUEAE0oxz.jpg:small
185 ms
Cdop11fVAAEvpeo.jpg:small
187 ms
CdoXEfGUkAAp6rZ.jpg:small
185 ms
Cdn0Rt5UUAAv_z2.jpg:small
188 ms
Cdm_GsNUsAAJYx6.jpg:small
187 ms
13670_10154838457725313_5241306057025408935_n.jpg
253 ms
safe_image.php
290 ms
safe_image.php
361 ms
safe_image.php
440 ms
10525971_10154837760125313_8661362520226478548_n.jpg
285 ms
12718063_10156580493175313_2244091185299903561_n.jpg
327 ms
12717942_10156569863275313_3471857216596176054_n.jpg
423 ms
12799055_10156569863270313_2727779331808188384_n.jpg
439 ms
wL6VQj7Ab77.png
118 ms
s7jcwEQH7Sx.png
119 ms
QDwYpIaRyfG.png
107 ms
K00K-UgnsKu.png
118 ms
jot
24 ms
I6-MnjEovm5.js
49 ms
pQrUxxo5oQp.js
80 ms
async-ads.js
32 ms
google_custom_search_watermark.gif
28 ms
small-logo.png
19 ms
search_box_icon.png
18 ms
clear.png
19 ms
pdx.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
Links do not have a discernible name
pdx.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pdx.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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pdx.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pdx.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.
pdx.com
Open Graph description is not detected on the main page of Pdx. 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: