Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

tennisphilly.com

Philly Tennis Community | The Metro Philadelphia Tennis League

Page Load Speed

1.8 sec in total

First Response

45 ms

Resources Loaded

1.6 sec

Page Rendered

220 ms

About Website

Click here to check amazing Tennis Philly content for United States. Otherwise, check out these important facts you probably never knew about tennisphilly.com

The Metro Philadelphia tennis league. We connect you with dedicated tennis partners on the courts. Servicing Montgomery County, West Philly, Philly city and New Jersey.

Visit tennisphilly.com

Key Findings

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

Performance Metrics

tennisphilly.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value4,220 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

tennisphilly.com

45 ms

www.tennisphilly.com

325 ms

style_new_home-a77ddff812d0014d2219258da6e9ca07.css

25 ms

general-3d13fdccc1e6a17a2d2f2e2ff9812cee.css

38 ms

bootstrap-6170f319dbd9ac5a4c6fdad4499fe6b1.css

63 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 79% of them (100 requests) were addressed to the original Tennisphilly.com, 3% (4 requests) were made to Facebook.com and 2% (3 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (325 ms) belongs to the original domain Tennisphilly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (31%)

Content Size

5.6 MB

After Optimization

3.9 MB

In fact, the total size of Tennisphilly.com main page is 5.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. 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 87.9 kB

  • Original 104.6 kB
  • After minification 96.4 kB
  • After compression 16.6 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 87.9 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 160.8 kB

  • Original 3.4 MB
  • After minification 3.3 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. Tennis Philly images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 933.3 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 471.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 933.3 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 551.1 kB

  • Original 639.1 kB
  • After minification 549.7 kB
  • After compression 88.0 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. Tennisphilly.com needs all CSS files to be minified and compressed as it can save up to 551.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 61 (50%)

Requests Now

122

After Optimization

61

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

Accessibility Review

tennisphilly.com accessibility score

60

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

tennisphilly.com SEO score

90

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

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