portauthority.org website review

15 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.2 s faster on a phone.

22 files are served with short cache lifetimes, so returning visitors download them again (3.1 MB).

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 12.0 s.

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.8 s faster on a phone.

About 429 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.

Your mobile performance score is 37 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

7 third-party services load with your homepage (kendostatic.com, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.8 MB and 802 ms of main-thread time.

156 KiB could be saved by minifying JavaScript.

3 long tasks block the main thread while loading, the longest for 807 ms. During a long task the page ignores taps.

kendostatic.com costs a phone 589 ms of main-thread work and 1.5 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

91 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The first text or image appears after 15.2 s on a phone. Good is under 1.8 s.

Your largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Connecting Communities”.

Visually, the page fills in at 15.2 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 24.0 s. Good is under 3.8 s.

Scripts block taps and scrolling for 757 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 90 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

Your homepage downloads 7.3 MB in 38 requests on a phone: images 4.6 MB (22), scripts 2.2 MB (10) and stylesheets 460 KiB (4). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

12 images (4.5 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

13 images further down the page (4.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example inclineclouds.png at 1,000 px wide, shown at 300 px. Resized copies would save about 379 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 2.07 g of CO₂e: 248.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must be contained by particular parents: 15 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

1 dropdown has no label.

Some list items are not inside a list.

1 element hidden from screen readers can still receive keyboard focus.

8 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with visible text labels do not have matching accessible names. (15 elements).

Your title is only 27 characters: “Pittsburgh Regional Transit”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 74 pages on portauthority.org and 11 external pages.

There is no https://rideprt.org/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://rideprt.org/Services, https://rideprt.org/fares-and-payment, https://rideprt.org/about-us, https://rideprt.org/contact-us, https://rideprt.org/Services/plan-your-trip and https://rideprt.org/Services/system-map and 9 others use the same meta description. A description written for each page earns more clicks.

https://rideprt.org/service-alerts-and-updates took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 55 found) and read each the way a search engine does.

9 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css2?family=Proxima+Nova:wght@400;700&display=swap' from orig…”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 958 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 7 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.