Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

phila.gov

City of Philadelphia

Page Load Speed

300 ms in total

First Response

49 ms

Resources Loaded

250 ms

Page Rendered

1 ms

phila.gov screenshot

About Website

Click here to check amazing Phila content for United States. Otherwise, check out these important facts you probably never knew about phila.gov

Official website of the City of Philadelphia, includes information on municipal services, permits, licenses, and records for citizens and businesses.

Visit phila.gov

Key Findings

We analyzed Phila.gov page load time and found that the first response time was 49 ms and then it took 251 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

phila.gov performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value5.9 s

49/100

10%

TBT (Total Blocking Time)

Value2,790 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value10.3 s

24/100

10%

Network Requests Diagram

www.phila.gov

49 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Phila.gov and no external sources were called. The less responsive or slowest element that took the longest time to load (49 ms) belongs to the original domain Phila.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (60%)

Content Size

3.3 MB

After Optimization

1.3 MB

In fact, the total size of Phila.gov main page is 3.3 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Javascripts take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-24%

Potential reduce by 53 B

  • Original 222 B
  • After minification 222 B
  • After compression 169 B

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 53 B or 24% of the original size.

Image Optimization

-9%

Potential reduce by 76.8 kB

  • Original 826.4 kB
  • After minification 749.6 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. Phila images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 1.6 MB

  • Original 2.1 MB
  • After minification 2.0 MB
  • After compression 525.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 1.6 MB or 75% of the original size.

CSS Optimization

-86%

Potential reduce by 318.1 kB

  • Original 368.2 kB
  • After minification 306.9 kB
  • After compression 50.1 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. Phila.gov needs all CSS files to be minified and compressed as it can save up to 318.1 kB or 86% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

phila.gov accessibility score

97

Accessibility Issues

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

phila.gov best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

phila.gov SEO score

89

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 Phila.gov 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 Phila.gov 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

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