Tools & Wizards About Us
portlandtransit.org screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

portlandtransit.org

Portland Transit -

Page Load Speed

4.3 sec in total

First Response

1.6 sec

Resources Loaded

2.4 sec

Page Rendered

246 ms

portlandtransit.org screenshot

About Website

Visit portlandtransit.org now to see the best up-to-date Portland Transit content and also check out these interesting facts you probably never knew about portlandtransit.org

Visit portlandtransit.org

Key Findings

We analyzed Portlandtransit.org page load time and found that the first response time was 1.6 sec and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

portlandtransit.org performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.212

59/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

portlandtransit.org

1560 ms

wp-emoji-release.min.js

169 ms

css

28 ms

bootstrap.css

226 ms

prettyPhoto.css

165 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 84% of them (27 requests) were addressed to the original Portlandtransit.org, 13% (4 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Portlandtransit.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 626.3 kB (47%)

Content Size

1.3 MB

After Optimization

706.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Portlandtransit.org 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. 50% of websites need less resources to load. Images take 573.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 13.0 kB

  • Original 17.4 kB
  • After minification 16.7 kB
  • After compression 4.4 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 13.0 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 19.6 kB

  • Original 573.6 kB
  • After minification 554.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. Portland Transit images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 293.5 kB

  • Original 370.5 kB
  • After minification 257.0 kB
  • After compression 77.0 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 293.5 kB or 79% of the original size.

CSS Optimization

-81%

Potential reduce by 300.1 kB

  • Original 370.8 kB
  • After minification 303.7 kB
  • After compression 70.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. Portlandtransit.org needs all CSS files to be minified and compressed as it can save up to 300.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (65%)

Requests Now

26

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portland Transit. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

portlandtransit.org

portlandtransit.org

1560 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

169 ms

css

css

28 ms

bootstrap.css

bootstrap.css

226 ms

prettyPhoto.css

prettyPhoto.css

165 ms

style-shortcodes.css

style-shortcodes.css

168 ms

style.css

style.css

230 ms

dashicons.min.css

dashicons.min.css

271 ms

font-awesome.css

font-awesome.css

244 ms

style-responsive.css

style-responsive.css

247 ms

jquery.js

jquery.js

374 ms

jquery-migrate.min.js

jquery-migrate.min.js

291 ms

imagesloaded.js

imagesloaded.js

240 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

251 ms

main-frontend.js

main-frontend.js

254 ms

bootstrap.js

bootstrap.js

281 ms

modernizr.js

modernizr.js

299 ms

masonry.js

masonry.js

308 ms

responsiveslides.js

responsiveslides.js

400 ms

responsiveslides-call.js

responsiveslides-call.js

400 ms

transparent.png

transparent.png

73 ms

slide_demo1.png

slide_demo1.png

541 ms

slide_demo2.png

slide_demo2.png

217 ms

slide_demo3.png

slide_demo3.png

208 ms

featured1.png

featured1.png

148 ms

featured2.png

featured2.png

143 ms

featured3.png

featured3.png

200 ms

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

10 ms

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

10 ms

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

58 ms

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

57 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

229 ms

Accessibility Review

portlandtransit.org accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

portlandtransit.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

portlandtransit.org SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portlandtransit.org 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 Portlandtransit.org 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.

Social Sharing Optimization

portlandtransit.org

Open Graph description is not detected on the main page of Portland Transit. 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: