Tools & Wizards About Us
washingtonwizardsblog.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

washingtonwizardsblog.com

Washington Wizards Blog: The Official Team Blog of the Wa | Washington Wizards Blog

Page Load Speed

74.9 sec in total

First Response

149 ms

Resources Loaded

43 sec

Page Rendered

31.8 sec

washingtonwizardsblog.com screenshot

About Website

Visit washingtonwizardsblog.com now to see the best up-to-date Washington Wizards Blog content and also check out these interesting facts you probably never knew about washingtonwizardsblog.com

Washington Wizards Blog includes Insights from Jeremy Hyman, Chris Gehring, Zach Rosen and Jacob Raim. Get an All-Access Pass to News, Transactions, & Stats on

Visit washingtonwizardsblog.com

Key Findings

We analyzed Washingtonwizardsblog.com page load time and found that the first response time was 149 ms and then it took 74.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

washingtonwizardsblog.com performance score

0

Network Requests Diagram

washingtonwizardsblog.com

149 ms

washingtonwizardsblog.monumentalsportsnetwork.com

1131 ms

jquery.min.js

852 ms

sdk.js

1255 ms

css

3111 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Washingtonwizardsblog.com, 17% (13 requests) were made to Snagfilms-a.akamaihd.net and 13% (10 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (9 sec) relates to the external source Monumentalsportsnetwork.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 898.5 kB (28%)

Content Size

3.2 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 174.5 kB

  • Original 217.6 kB
  • After minification 206.9 kB
  • After compression 43.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 174.5 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 12.7 kB

  • Original 2.0 MB
  • After minification 2.0 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. Washington Wizards Blog images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 351.2 kB

  • Original 568.9 kB
  • After minification 568.8 kB
  • After compression 217.8 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 351.2 kB or 62% of the original size.

CSS Optimization

-85%

Potential reduce by 360.1 kB

  • Original 422.2 kB
  • After minification 420.9 kB
  • After compression 62.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. Washingtonwizardsblog.com needs all CSS files to be minified and compressed as it can save up to 360.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (40%)

Requests Now

68

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

washingtonwizardsblog.com

washingtonwizardsblog.com

149 ms

washingtonwizardsblog.monumentalsportsnetwork.com

washingtonwizardsblog.monumentalsportsnetwork.com

1131 ms

jquery.min.js

jquery.min.js

852 ms

sdk.js

sdk.js

1255 ms

css

css

3111 ms

monumental-network.525e1cfd0ad997985e83de2b0ee928e9.gz.css

monumental-network.525e1cfd0ad997985e83de2b0ee928e9.gz.css

3167 ms

lodash.min.js

lodash.min.js

2708 ms

require.min.js

require.min.js

2708 ms

First+Month+Free+300x600.gif

First+Month+Free+300x600.gif

7858 ms

monumental-logo-svg.svg

monumental-logo-svg.svg

2146 ms

capitals-mark.svg

capitals-mark.svg

4605 ms

wizards-logo-svg.svg

wizards-logo-svg.svg

5629 ms

mystics-logo-svg.svg

mystics-logo-svg.svg

5594 ms

monumental-sports-network-tm-logo-horizontal-small.png

monumental-sports-network-tm-logo-horizontal-small.png

5012 ms

logo-affiliates.png

logo-affiliates.png

5628 ms

washington-wizards-logo.svg

washington-wizards-logo.svg

5631 ms

collapsed-monumental-logo.png

collapsed-monumental-logo.png

5069 ms

empty-blog-logo.png

empty-blog-logo.png

5557 ms

godaddy-sslm.png

godaddy-sslm.png

7196 ms

washingtonwizardsblog-headshot.png

washingtonwizardsblog-headshot.png

7736 ms

gtm.js

gtm.js

8137 ms

masthead-authentication-widget

masthead-authentication-widget

9045 ms

washington-wizards-blog-centered-banner.jpg

washington-wizards-blog-centered-banner.jpg

5709 ms

dfp.jsp

dfp.jsp

1836 ms

6515 ms

dfp.jsp

dfp.jsp

3920 ms

6518 ms

6234 ms

7624 ms

7623 ms

7623 ms

7621 ms

7854 ms

7855 ms

8396 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

6233 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

6499 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

7549 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

7781 ms

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

7782 ms

dfp.jsp

dfp.jsp

3432 ms

gpt.js

gpt.js

6268 ms

initialize.js

initialize.js

1657 ms

analytics.js

analytics.js

3559 ms

handlebars.min.js

handlebars.min.js

1602 ms

bootstrap-3.2.0.min.js

bootstrap-3.2.0.min.js

1343 ms

URI.js

URI.js

1880 ms

modernizr.custom.js

modernizr.custom.js

1342 ms

backbone-min.js

backbone-min.js

1198 ms

pubads_impl_147.js

pubads_impl_147.js

594 ms

collect

collect

116 ms

ads

ads

561 ms

ads

ads

942 ms

container.html

container.html

1678 ms

ads

ads

981 ms

ads

ads

423 ms

ads

ads

984 ms

ads

ads

104 ms

12607616954062939559

12607616954062939559

916 ms

m_window_focus_non_hydra.js

m_window_focus_non_hydra.js

1348 ms

osd_listener.js

osd_listener.js

1379 ms

osd.js

osd.js

2824 ms

6198354624496010032

6198354624496010032

806 ms

12957862493288701233

12957862493288701233

806 ms

11494208999705785357

11494208999705785357

1527 ms

10813698460738875491

10813698460738875491

1528 ms

2729236593617757465

2729236593617757465

1086 ms

initialize.js

initialize.js

1085 ms

collect

collect

1223 ms

collect

collect

638 ms

bootstrap-3.2.0.min.js

bootstrap-3.2.0.min.js

95 ms

URI.js

URI.js

48 ms

modernizr.custom.js

modernizr.custom.js

406 ms

rum.js

rum.js

294 ms

activeview

activeview

298 ms

SEO Factors

washingtonwizardsblog.com SEO score

0

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

washingtonwizardsblog.com

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