Tools & Wizards About Us
whatnowphilly.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

whatnowphilly.com

What Now Philly: The Best Source For Philadelphia News

Page Load Speed

1.4 sec in total

First Response

206 ms

Resources Loaded

722 ms

Page Rendered

475 ms

whatnowphilly.com screenshot

About Website

Visit whatnowphilly.com now to see the best up-to-date What Now Philly content and also check out these interesting facts you probably never knew about whatnowphilly.com

What Now Philadelphia is the premier news source for planned restaurants, retail, and real estate in the Philadelphia, PA area. Learn what's trending in PHILLY today!

Visit whatnowphilly.com

Key Findings

We analyzed Whatnowphilly.com page load time and found that the first response time was 206 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

whatnowphilly.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value1,110 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

whatnowphilly.com

206 ms

gppstub.js

163 ms

frontend.min.css

31 ms

jquery.min.js

34 ms

jquery-migrate.min.js

34 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 84% of them (52 requests) were addressed to the original Whatnowphilly.com, 3% (2 requests) were made to The.gatekeeperconsent.com and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (214 ms) relates to the external source The.gatekeeperconsent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 253.6 kB (22%)

Content Size

1.2 MB

After Optimization

902.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatnowphilly.com main page is 1.2 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. 60% of websites need less resources to load. Images take 519.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 245.5 kB

  • Original 297.6 kB
  • After minification 297.6 kB
  • After compression 52.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. 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 245.5 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 4.7 kB

  • Original 519.0 kB
  • After minification 514.4 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. What Now Philly images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.4 kB

  • Original 338.9 kB
  • After minification 338.9 kB
  • After compression 335.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 19 B

  • Original 178 B
  • After minification 178 B
  • After compression 159 B

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. Whatnowphilly.com needs all CSS files to be minified and compressed as it can save up to 19 B or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (92%)

Requests Now

60

After Optimization

5

  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Now 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 56 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

whatnowphilly.com

whatnowphilly.com

206 ms

gppstub.js

gppstub.js

163 ms

frontend.min.css

frontend.min.css

31 ms

jquery.min.js

jquery.min.js

34 ms

jquery-migrate.min.js

jquery-migrate.min.js

34 ms

v4-shims.min.js

v4-shims.min.js

34 ms

js

js

112 ms

photoswipe.min.js

photoswipe.min.js

47 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

93 ms

swiper-bundle.min.js

swiper-bundle.min.js

53 ms

ccpaplus.js

ccpaplus.js

214 ms

email-decode.min.js

email-decode.min.js

34 ms

thickbox.js

thickbox.js

44 ms

terms.js

terms.js

43 ms

filter-list.js

filter-list.js

41 ms

script-config.js

script-config.js

51 ms

jquery.fittext.js

jquery.fittext.js

42 ms

wpdiscuz-combo.min.js

wpdiscuz-combo.min.js

51 ms

idle-timer.min.js

idle-timer.min.js

51 ms

custom.js

custom.js

52 ms

hello-frontend.min.js

hello-frontend.min.js

56 ms

common.js

common.js

53 ms

leaflet.js

leaflet.js

64 ms

wna-leaflet.js

wna-leaflet.js

61 ms

OneSignalSDK.js

OneSignalSDK.js

48 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

66 ms

imagesloaded.min.js

imagesloaded.min.js

61 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

62 ms

webpack.runtime.min.js

webpack.runtime.min.js

64 ms

frontend-modules.min.js

frontend-modules.min.js

208 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

73 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

73 ms

wp-polyfill.min.js

wp-polyfill.min.js

82 ms

hooks.min.js

hooks.min.js

76 ms

i18n.min.js

i18n.min.js

75 ms

frontend.min.js

frontend.min.js

91 ms

waypoints.min.js

waypoints.min.js

83 ms

core.min.js

core.min.js

91 ms

frontend.min.js

frontend.min.js

89 ms

elements-handlers.min.js

elements-handlers.min.js

93 ms

jquery.sticky.min.js

jquery.sticky.min.js

108 ms

slick.min.js

slick.min.js

31 ms

v.js

v.js

204 ms

swiper-bundle.min.js

swiper-bundle.min.js

16 ms

boise.js

boise.js

50 ms

abilene.js

abilene.js

50 ms

tulsa.js

tulsa.js

50 ms

et.js

et.js

46 ms

lazy_load.js

lazy_load.js

29 ms

Gouldsburger-express.png

Gouldsburger-express.png

130 ms

mulvane.js

mulvane.js

41 ms

wichita.js

wichita.js

47 ms

raleigh.js

raleigh.js

41 ms

vista.js

vista.js

40 ms

olathe.js

olathe.js

42 ms

frontend.min.css

frontend.min.css

29 ms

css_onload.js

css_onload.js

45 ms

vitals.js

vitals.js

26 ms

drake.js

drake.js

27 ms

chanute.js

chanute.js

27 ms

jellyfish.js

jellyfish.js

27 ms

loadingAnimation.gif

loadingAnimation.gif

18 ms

Accessibility Review

whatnowphilly.com accessibility score

88

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

whatnowphilly.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

whatnowphilly.com SEO score

99

Search Engine Optimization Advices

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 Whatnowphilly.com 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 Whatnowphilly.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.

Social Sharing Optimization

whatnowphilly.com

Open Graph data is detected on the main page of What Now Philly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: