Tools & Wizards About Us
pistons.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

pistons.com

Pistons - The official site of the NBA for the latest NBA Scores, Stats & News. | NBA.com

Page Load Speed

857 ms in total

First Response

43 ms

Resources Loaded

738 ms

Page Rendered

76 ms

pistons.com screenshot

About Website

Welcome to pistons.com homepage info - get ready to check Pistons best content right away, or after learning these important things about pistons.com

The official site of the National Basketball Association. Follow the action on NBA scores, schedules, stats, news, Team and Player news.

Visit pistons.com

Key Findings

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

Performance Metrics

pistons.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value39.2 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value8,810 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.193

64/100

15%

TTI (Time to Interactive)

Value39.0 s

0/100

10%

Network Requests Diagram

pistons.com

43 ms

450 ms

037be56f1290d04b.css

18 ms

801fe7d3bc269a8d.css

37 ms

7728bb5a9e66b7ed.css

45 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pistons.com, 97% (37 requests) were made to Nba.com. The less responsive or slowest element that took the longest time to load (450 ms) relates to the external source Nba.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 267.2 kB (69%)

Content Size

388.0 kB

After Optimization

120.8 kB

  • HTML
  • JavaScript

In fact, the total size of Pistons.com main page is 388.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 232.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 124.6 kB

  • Original 155.9 kB
  • After minification 155.5 kB
  • After compression 31.2 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 124.6 kB or 80% of the original size.

JavaScript Optimization

-61%

Potential reduce by 142.6 kB

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

Requests Breakdown

Number of requests can be reduced by 34 (94%)

Requests Now

36

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

pistons.com

pistons.com

43 ms

450 ms

037be56f1290d04b.css

037be56f1290d04b.css

18 ms

801fe7d3bc269a8d.css

801fe7d3bc269a8d.css

37 ms

7728bb5a9e66b7ed.css

7728bb5a9e66b7ed.css

45 ms

d1385183d1eb8f98.css

d1385183d1eb8f98.css

39 ms

25536ee16e462120.css

25536ee16e462120.css

32 ms

0df8905e5582f0ae.css

0df8905e5582f0ae.css

30 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

43 ms

webpack-290aeb299be310ac.js

webpack-290aeb299be310ac.js

51 ms

framework-43593b4bbeb0cf4e.js

framework-43593b4bbeb0cf4e.js

52 ms

main-00165ecff087b64a.js

main-00165ecff087b64a.js

53 ms

_app-f73d1b956abcac9c.js

_app-f73d1b956abcac9c.js

52 ms

d6e1aeb5-aafa43b96e622573.js

d6e1aeb5-aafa43b96e622573.js

54 ms

e28bfcc5-b78f41149a18db6c.js

e28bfcc5-b78f41149a18db6c.js

57 ms

1655-59570475cc813b68.js

1655-59570475cc813b68.js

55 ms

8052-1bc5364e472e9934.js

8052-1bc5364e472e9934.js

55 ms

2832-3cbb1e497bdfce60.js

2832-3cbb1e497bdfce60.js

57 ms

5263-5b63a0e979291095.js

5263-5b63a0e979291095.js

57 ms

2605-d3c161d0f901ddf5.js

2605-d3c161d0f901ddf5.js

59 ms

1758-69a8e55178eb61ae.js

1758-69a8e55178eb61ae.js

66 ms

4360-4b89cfe93ab64652.js

4360-4b89cfe93ab64652.js

65 ms

4060-98737f857ace3514.js

4060-98737f857ace3514.js

70 ms

1697-a9fd3d5f9fa4dab3.js

1697-a9fd3d5f9fa4dab3.js

65 ms

5116-e91e0252e77e3a09.js

5116-e91e0252e77e3a09.js

68 ms

9076-0a06aa14320d743c.js

9076-0a06aa14320d743c.js

76 ms

2083-e46d6ec2a5ad4159.js

2083-e46d6ec2a5ad4159.js

87 ms

6141-46b872e63613e9fd.js

6141-46b872e63613e9fd.js

74 ms

2044-b870e13483bd5b57.js

2044-b870e13483bd5b57.js

76 ms

5096-99ecc5b1e93734b4.js

5096-99ecc5b1e93734b4.js

82 ms

7068-d705b9d354882286.js

7068-d705b9d354882286.js

224 ms

6991-b1403b8128389037.js

6991-b1403b8128389037.js

85 ms

5911-83dae23167c89edc.js

5911-83dae23167c89edc.js

222 ms

1538-7f1beb48dd984265.js

1538-7f1beb48dd984265.js

86 ms

%5Bteamslug%5D-7a1872bac8e9baa0.js

%5Bteamslug%5D-7a1872bac8e9baa0.js

95 ms

_buildManifest.js

_buildManifest.js

98 ms

_ssgManifest.js

_ssgManifest.js

98 ms

BUXIB

BUXIB

96 ms

Accessibility Review

pistons.com accessibility score

92

Accessibility Issues

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-*] attributes do not match their roles

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

pistons.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pistons.com SEO score

98

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

pistons.com

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