Tools & Wizards About Us
phillyfamily.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

phillyfamily.com

Philadelphia Family | Building Community to Connect Local Parents with Resources, Events, and Each Other!

Page Load Speed

2.1 sec in total

First Response

86 ms

Resources Loaded

1.1 sec

Page Rendered

904 ms

phillyfamily.com screenshot

About Website

Welcome to phillyfamily.com homepage info - get ready to check Philly Family best content for United States right away, or after learning these important things about phillyfamily.com

Philadelphia Family connects parents with resources, fun things to do, and connection with our magazine, newsletter, events, and social media community.

Visit phillyfamily.com

Key Findings

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

Performance Metrics

phillyfamily.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

phillyfamily.com

86 ms

phillyfamily.com

114 ms

style-blocks.build.css

14 ms

tribe-events-pro-mini-calendar-block.min.css

27 ms

style.min.css

39 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 75% of them (62 requests) were addressed to the original Phillyfamily.com, 23% (19 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (327 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 283.8 kB (21%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phillyfamily.com main page is 1.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 675.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 269.1 kB

  • Original 300.0 kB
  • After minification 285.3 kB
  • After compression 30.9 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 269.1 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 675.5 kB
  • After minification 675.5 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. Philly Family images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 5.9 kB

  • Original 205.5 kB
  • After minification 205.5 kB
  • After compression 199.6 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

-5%

Potential reduce by 8.8 kB

  • Original 181.1 kB
  • After minification 180.8 kB
  • After compression 172.3 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. Phillyfamily.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (87%)

Requests Now

60

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phillyfamily.com

phillyfamily.com

86 ms

phillyfamily.com

phillyfamily.com

114 ms

style-blocks.build.css

style-blocks.build.css

14 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

27 ms

style.min.css

style.min.css

39 ms

style.css

style.css

27 ms

modules.min.css

modules.min.css

42 ms

font-awesome.min.css

font-awesome.min.css

35 ms

style.min.css

style.min.css

36 ms

style.css

style.css

51 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

51 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

54 ms

style_dynamic.css

style_dynamic.css

53 ms

modules-responsive.min.css

modules-responsive.min.css

54 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

61 ms

js_composer.min.css

js_composer.min.css

80 ms

css

css

74 ms

style.css

style.css

62 ms

leaflet.css

leaflet.css

97 ms

openstreet.css

openstreet.css

97 ms

public-main.css

public-main.css

101 ms

select2.css

select2.css

119 ms

ez-media-uploader.css

ez-media-uploader.css

98 ms

slick.css

slick.css

125 ms

sweetalert.css

sweetalert.css

123 ms

jquery.min.js

jquery.min.js

124 ms

jquery-migrate.min.js

jquery-migrate.min.js

120 ms

track-the-click-public.js

track-the-click-public.js

121 ms

js

js

71 ms

dismiss.js

dismiss.js

118 ms

core.min.js

core.min.js

231 ms

tabs.min.js

tabs.min.js

233 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

235 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

232 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

275 ms

jquery.appear.js

jquery.appear.js

274 ms

modernizr.custom.85257.js

modernizr.custom.85257.js

274 ms

hoverIntent.min.js

hoverIntent.min.js

275 ms

jquery.plugin.js

jquery.plugin.js

276 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

276 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

273 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

263 ms

select2.min.js

select2.min.js

261 ms

fluidvids.min.js

fluidvids.min.js

253 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

250 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

240 ms

TweenLite.min.js

TweenLite.min.js

243 ms

jquery.infinitescroll.min.js

jquery.infinitescroll.min.js

239 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

237 ms

slick.min.js

slick.min.js

240 ms

jquery.waitforimages.js

jquery.waitforimages.js

238 ms

modules.min.js

modules.min.js

238 ms

comment-reply.min.js

comment-reply.min.js

233 ms

js_composer_front.min.js

js_composer_front.min.js

232 ms

like.js

like.js

198 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

197 ms

Things-To-Do-This-Weekend-With-Your-Kids-4.gif

Things-To-Do-This-Weekend-With-Your-Kids-4.gif

115 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

198 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

217 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

219 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

218 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

219 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

219 ms

ElegantIcons.woff

ElegantIcons.woff

154 ms

PN_yRfK9oXHga0XV3e0qjBzT.ttf

PN_yRfK9oXHga0XV3e0qjBzT.ttf

267 ms

PN_yRfK9oXHga0XVwe4qjBzT.ttf

PN_yRfK9oXHga0XVwe4qjBzT.ttf

269 ms

PN_yRfK9oXHga0XV5e8qjBzT.ttf

PN_yRfK9oXHga0XV5e8qjBzT.ttf

268 ms

PN_yRfK9oXHga0XVuewqjBzT.ttf

PN_yRfK9oXHga0XVuewqjBzT.ttf

326 ms

PN_xRfK9oXHga0XdaMg6.ttf

PN_xRfK9oXHga0XdaMg6.ttf

269 ms

PN_yRfK9oXHga0XVzeoqjBzT.ttf

PN_yRfK9oXHga0XVzeoqjBzT.ttf

327 ms

PN_yRfK9oXHga0XVqekqjBzT.ttf

PN_yRfK9oXHga0XVqekqjBzT.ttf

274 ms

linea-arrows-10.woff

linea-arrows-10.woff

152 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf

269 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf

269 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf

270 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWV4exQ.ttf

271 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf

270 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf

271 ms

PF-Masthead-Logo_Final-e1709684044613.png

PF-Masthead-Logo_Final-e1709684044613.png

196 ms

Indoor-Water-Parks-main-line-parent.jpg

Indoor-Water-Parks-main-line-parent.jpg

195 ms

Weekend-Planner-675x675.png

Weekend-Planner-675x675.png

203 ms

Philadelphia-Dance-Academy-young-dancers-holding-hands.jpg

Philadelphia-Dance-Academy-young-dancers-holding-hands.jpg

148 ms

philly-family-back-to-school-guide-cover-675x675.gif

philly-family-back-to-school-guide-cover-675x675.gif

203 ms

Accessibility Review

phillyfamily.com accessibility score

71

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

phillyfamily.com SEO score

86

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

High

robots.txt is not valid

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

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

phillyfamily.com

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