Tools & Wizards About Us
opendataphilly.org screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

opendataphilly.org

OpenDataPhilly

Page Load Speed

5.8 sec in total

First Response

162 ms

Resources Loaded

4.9 sec

Page Rendered

703 ms

opendataphilly.org screenshot

About Website

Click here to check amazing Open Data Philly content for United States. Otherwise, check out these important facts you probably never knew about opendataphilly.org

OpenDataPhilly is a catalog of open data in the Philadelphia region. In addition to being the official open data repository for the City of Philadelphia, it includes data sets from many organizations ...

Visit opendataphilly.org

Key Findings

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

Performance Metrics

opendataphilly.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value13,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

opendataphilly.org

162 ms

www.opendataphilly.org

953 ms

select2.css

284 ms

main.min.css

843 ms

font-awesome.min.css

287 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 50% of them (32 requests) were addressed to the original Opendataphilly.org, 16% (10 requests) were made to Pbs.twimg.com and 8% (5 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source S3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 802.7 kB (18%)

Content Size

4.6 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Opendataphilly.org main page is 4.6 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. 45% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 41.8 kB

  • Original 50.9 kB
  • After minification 41.3 kB
  • After compression 9.1 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 9.6 kB, which is 19% 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 41.8 kB or 82% of the original size.

Image Optimization

-10%

Potential reduce by 402.1 kB

  • Original 4.0 MB
  • After minification 3.6 MB

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. Open Data Philly images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 185.7 kB

  • Original 279.0 kB
  • After minification 277.5 kB
  • After compression 93.2 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 185.7 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 173.1 kB

  • Original 208.0 kB
  • After minification 200.9 kB
  • After compression 34.9 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. Opendataphilly.org needs all CSS files to be minified and compressed as it can save up to 173.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (20%)

Requests Now

60

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

opendataphilly.org

opendataphilly.org

162 ms

www.opendataphilly.org

www.opendataphilly.org

953 ms

select2.css

select2.css

284 ms

main.min.css

main.min.css

843 ms

font-awesome.min.css

font-awesome.min.css

287 ms

main.css

main.css

295 ms

css

css

370 ms

jquery.min.js

jquery.min.js

614 ms

select2.min.js

select2.min.js

569 ms

image-upload.min.js

image-upload.min.js

712 ms

googleanalytics_event_tracking.js

googleanalytics_event_tracking.js

376 ms

favorite.js

favorite.js

397 ms

analytics.js

analytics.js

876 ms

geohistory.png

geohistory.png

2690 ms

CQPxHs2UEAA9fYm.jpg

CQPxHs2UEAA9fYm.jpg

502 ms

6ae280960.png

6ae280960.png

597 ms

logo_color.svg

logo_color.svg

481 ms

Map-ward-leaders-in-Philadelphia-city-committee-.jpg

Map-ward-leaders-in-Philadelphia-city-committee-.jpg

313 ms

20150706-PPA-Parking-ticket.jpg

20150706-PPA-Parking-ticket.jpg

452 ms

170.png

170.png

991 ms

screenshot.png

screenshot.png

1560 ms

vglefo.png

vglefo.png

1306 ms

PHL%20Maps%20w%20Pattern%20Colors.png

PHL%20Maps%20w%20Pattern%20Colors.png

727 ms

day-by-day-usage-patterns-11th-Reed.png

day-by-day-usage-patterns-11th-Reed.png

1278 ms

COoF04QWoAA4Uay.jpg

COoF04QWoAA4Uay.jpg

868 ms

CN54BbtWgAAhUUK.jpg:large

CN54BbtWgAAhUUK.jpg:large

567 ms

CNhQ_fdWgAAUrXZ.png

CNhQ_fdWgAAUrXZ.png

564 ms

CQz3rVeWUAE0r03.jpg

CQz3rVeWUAE0r03.jpg

712 ms

CTYGqWzXIAEXIZl.jpg

CTYGqWzXIAEXIZl.jpg

867 ms

CWD2A24WcAEBPTh.png:large

CWD2A24WcAEBPTh.png:large

1426 ms

CVJW8rBWUAArIdF.png

CVJW8rBWUAArIdF.png

1473 ms

CaY0qrHWEAAngd1.png

CaY0qrHWEAAngd1.png

2386 ms

CTdw7XKXIAADkjP.jpg

CTdw7XKXIAADkjP.jpg

1016 ms

walkshed.jpg

walkshed.jpg

641 ms

school-budget.png

school-budget.png

1426 ms

stief.jpg

stief.jpg

1295 ms

tax-delinquency.png

tax-delinquency.png

2944 ms

odp-logo.png

odp-logo.png

271 ms

larrow.svg

larrow.svg

266 ms

rarrow.svg

rarrow.svg

270 ms

20141223-193733.151747iconsart.svg

20141223-193733.151747iconsart.svg

273 ms

20141223-193756.990691iconsbudget.svg

20141223-193756.990691iconsbudget.svg

267 ms

20141223-193813.665606iconseconomy.svg

20141223-193813.665606iconseconomy.svg

271 ms

20141223-194239.846305iconseducation.svg

20141223-194239.846305iconseducation.svg

285 ms

20141223-193842.916844iconselections.svg

20141223-193842.916844iconselections.svg

603 ms

20141223-194254.915092iconsenvironment.svg

20141223-194254.915092iconsenvironment.svg

612 ms

20141223-194334.639060iconsfood.svg

20141223-194334.639060iconsfood.svg

609 ms

20141223-194316.223437iconshealth.svg

20141223-194316.223437iconshealth.svg

1173 ms

20141223-194351.335866iconsparks.svg

20141223-194351.335866iconsparks.svg

1184 ms

20141223-194423.154603iconsplanning.svg

20141223-194423.154603iconsplanning.svg

358 ms

20141223-194440.888468iconspublicsafety.svg

20141223-194440.888468iconspublicsafety.svg

409 ms

20141223-194406.761461iconsrealestate.svg

20141223-194406.761461iconsrealestate.svg

467 ms

20141223-194455.342914iconstransportation.svg

20141223-194455.342914iconstransportation.svg

970 ms

20141223-194512.006490iconsdocument.svg

20141223-194512.006490iconsdocument.svg

676 ms

gtm.js

gtm.js

415 ms

widgets.js

widgets.js

740 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

903 ms

viz-partial-crime

viz-partial-crime

500 ms

en

en

467 ms

odp-viz-1.png

odp-viz-1.png

800 ms

linkid.js

linkid.js

57 ms

collect

collect

100 ms

collect

collect

364 ms

collect

collect

158 ms

Accessibility Review

opendataphilly.org accessibility score

82

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

opendataphilly.org best practices score

83

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

SEO Factors

opendataphilly.org SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Opendataphilly.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 Opendataphilly.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

opendataphilly.org

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