Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 41

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

playlocal.com

PlayLocal - Find local tennis players and reserve public courts

Page Load Speed

714 ms in total

First Response

65 ms

Resources Loaded

477 ms

Page Rendered

172 ms

playlocal.com screenshot

About Website

Visit playlocal.com now to see the best up-to-date Play Local content and also check out these interesting facts you probably never knew about playlocal.com

Spend your time playing tennis instead of searching for people to play or waiting for a court. Play More, Play Local.

Visit playlocal.com

Key Findings

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

Performance Metrics

playlocal.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value1.001

2/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

playlocal.com

65 ms

www.playlocal.com

90 ms

css

48 ms

css

65 ms

init_application-1e3dc6bf1ea5b4cbed376badd79eb856a2f2b75333e9bcc4a94b33810a827e95.css

35 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Playlocal.com, 44% (15 requests) were made to D34os8bs8ae6o7.cloudfront.net and 21% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (152 ms) relates to the external source Maps.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 433.8 kB (27%)

Content Size

1.6 MB

After Optimization

1.2 MB

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

HTML Optimization

-68%

Potential reduce by 35.4 kB

  • Original 52.2 kB
  • After minification 51.5 kB
  • After compression 16.8 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 35.4 kB or 68% of the original size.

Image Optimization

-12%

Potential reduce by 117.6 kB

  • Original 992.0 kB
  • After minification 874.3 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. Obviously, Play Local needs image optimization as it can save up to 117.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-52%

Potential reduce by 266.0 kB

  • Original 515.5 kB
  • After minification 515.4 kB
  • After compression 249.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 266.0 kB or 52% of the original size.

CSS Optimization

-26%

Potential reduce by 14.8 kB

  • Original 57.9 kB
  • After minification 57.9 kB
  • After compression 43.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. Playlocal.com needs all CSS files to be minified and compressed as it can save up to 14.8 kB or 26% of the original size.

Requests Breakdown

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

Requests Now

25

After Optimization

20

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

Accessibility Review

playlocal.com accessibility score

41

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

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

playlocal.com SEO score

85

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

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Playlocal.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Playlocal.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 Play Local. 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: