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.
{{url}}
{{time}} 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.
{{og_description}}
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: