Tools & Wizards About Us
mybrokenleg.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mybrokenleg.com

MyBrokenLeg.com - Broken leg stories and advice

Page Load Speed

2.7 sec in total

First Response

621 ms

Resources Loaded

1.9 sec

Page Rendered

88 ms

mybrokenleg.com screenshot

About Website

Visit mybrokenleg.com now to see the best up-to-date My Broken Leg content for United States and also check out these interesting facts you probably never knew about mybrokenleg.com

MyBrokenLeg.com - the site for people with a broken leg.

Visit mybrokenleg.com

Key Findings

We analyzed Mybrokenleg.com page load time and found that the first response time was 621 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

mybrokenleg.com performance score

0

Network Requests Diagram

mybrokenleg.com

621 ms

main.css

376 ms

show_ads.js

5 ms

pixel.gif

1375 ms

logo.gif

1435 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 31% of them (4 requests) were addressed to the original Mybrokenleg.com, 31% (4 requests) were made to Pagead2.googlesyndication.com and 15% (2 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Mybrokenleg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 196.4 kB (56%)

Content Size

353.8 kB

After Optimization

157.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mybrokenleg.com main page is 353.8 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. 20% of websites need less resources to load. Javascripts take 328.1 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 8.0 kB

  • Original 11.1 kB
  • After minification 10.9 kB
  • After compression 3.0 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 8.0 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 191 B

  • Original 13.6 kB
  • After minification 13.4 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. My Broken Leg images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 187.4 kB

  • Original 328.1 kB
  • After minification 327.9 kB
  • After compression 140.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 187.4 kB or 57% of the original size.

CSS Optimization

-77%

Potential reduce by 778 B

  • Original 1.0 kB
  • After minification 810 B
  • After compression 237 B

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. Mybrokenleg.com needs all CSS files to be minified and compressed as it can save up to 778 B or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (36%)

Requests Now

11

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mybrokenleg.com

mybrokenleg.com

621 ms

main.css

main.css

376 ms

show_ads.js

show_ads.js

5 ms

pixel.gif

pixel.gif

1375 ms

logo.gif

logo.gif

1435 ms

cmp.php

cmp.php

148 ms

ca-pub-5100956353815720.js

ca-pub-5100956353815720.js

52 ms

zrt_lookup.html

zrt_lookup.html

50 ms

show_ads_impl.js

show_ads_impl.js

58 ms

ga.js

ga.js

14 ms

__utm.gif

__utm.gif

15 ms

ads

ads

177 ms

osd.js

osd.js

3 ms

SEO Factors

mybrokenleg.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mybrokenleg.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 Mybrokenleg.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

mybrokenleg.com

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