Tools & Wizards About Us
blog.draftstars.com.au screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

blog.draftstars.com.au

Draftstars Blog - News and Information on AFL, NRL, NBA, NFL and Fantasy Sports. - Draftstars

Page Load Speed

1.1 sec in total

First Response

103 ms

Resources Loaded

754 ms

Page Rendered

269 ms

blog.draftstars.com.au screenshot

About Website

Click here to check amazing Blog Draftstars content for Australia. Otherwise, check out these important facts you probably never knew about blog.draftstars.com.au

Head to The Huddle from Draftstars for the latest player news, fantasy tips, best buys and much more!

Visit blog.draftstars.com.au

Key Findings

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

Performance Metrics

blog.draftstars.com.au performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value2,500 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value30.4 s

0/100

10%

Network Requests Diagram

blog.draftstars.com.au

103 ms

ddp1.min.css

41 ms

brand.min.css

60 ms

style.css

107 ms

style.min.css

95 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 57% of them (31 requests) were addressed to the original Blog.draftstars.com.au, 6% (3 requests) were made to Fonts.googleapis.com and 6% (3 requests) were made to D269xv2m34uktg.cloudfront.net. The less responsive or slowest element that took the longest time to load (286 ms) belongs to the original domain Blog.draftstars.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 414.6 kB (17%)

Content Size

2.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.draftstars.com.au main page is 2.5 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. 50% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 60.7 kB

  • Original 74.8 kB
  • After minification 64.7 kB
  • After compression 14.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. This page needs HTML code to be minified as it can gain 10.1 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 60.7 kB or 81% of the original size.

Image Optimization

-15%

Potential reduce by 341.4 kB

  • Original 2.3 MB
  • After minification 1.9 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. Obviously, Blog Draftstars needs image optimization as it can save up to 341.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 379 B

  • Original 67.0 kB
  • After minification 67.0 kB
  • After compression 66.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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 12.1 kB

  • Original 109.0 kB
  • After minification 109.0 kB
  • After compression 96.9 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. Blog.draftstars.com.au needs all CSS files to be minified and compressed as it can save up to 12.1 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (55%)

Requests Now

44

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.draftstars.com.au

blog.draftstars.com.au

103 ms

ddp1.min.css

ddp1.min.css

41 ms

brand.min.css

brand.min.css

60 ms

style.css

style.css

107 ms

style.min.css

style.min.css

95 ms

jquery.min.js

jquery.min.js

21 ms

scripts.min.js

scripts.min.js

69 ms

script.js

script.js

63 ms

jquery-mobile-swipe.js

jquery-mobile-swipe.js

71 ms

widgets.js

widgets.js

14 ms

bootstrap.css

bootstrap.css

62 ms

css

css

29 ms

font-awesome.min.css

font-awesome.min.css

27 ms

nanoscroller.css

nanoscroller.css

55 ms

jquery.nouislider.css

jquery.nouislider.css

59 ms

hopscotch-0.1.2.css

hopscotch-0.1.2.css

67 ms

magnific-popup.css

magnific-popup.css

86 ms

pops.css

pops.css

97 ms

css

css

22 ms

css

css

21 ms

dc.js

dc.js

24 ms

v1.js

v1.js

24 ms

index_header_logo_draftstars.png

index_header_logo_draftstars.png

89 ms

the_huddle_logo.png

the_huddle_logo.png

88 ms

Fantasy-Insider-on-Draftstars-1024x536.jpg

Fantasy-Insider-on-Draftstars-1024x536.jpg

157 ms

Blog-Post-03.03.2020-Pic-1-.png

Blog-Post-03.03.2020-Pic-1-.png

286 ms

image-32.png

image-32.png

220 ms

header.png

header.png

254 ms

ds_thehangerover.jpg

ds_thehangerover.jpg

230 ms

Donic-v-Young.png

Donic-v-Young.png

241 ms

footer_logo_star.png

footer_logo_star.png

178 ms

fb_icon_white.png

fb_icon_white.png

210 ms

twitter_icon_white.png

twitter_icon_white.png

240 ms

instagram_icon_white.png

instagram_icon_white.png

249 ms

footer_sub_logo_draftstars.png

footer_sub_logo_draftstars.png

261 ms

font

font

95 ms

sdk.js

sdk.js

92 ms

__utm.gif

__utm.gif

15 ms

font

font

19 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

237 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

189 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

12 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

19 ms

asset_composer.js

asset_composer.js

72 ms

gtm.js

gtm.js

101 ms

sdk.js

sdk.js

33 ms

glyphicons-halflings-regular.ttf

glyphicons-halflings-regular.ttf

3 ms

34 ms

glyphicons-halflings-regular.svg

glyphicons-halflings-regular.svg

4 ms

glyphicons-halflings-regular.ttf

glyphicons-halflings-regular.ttf

35 ms

track

track

27 ms

glyphicons-halflings-regular.svg

glyphicons-halflings-regular.svg

32 ms

page.php

page.php

96 ms

LO_ZbPzgR8d.css

LO_ZbPzgR8d.css

15 ms

Accessibility Review

blog.draftstars.com.au accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

blog.draftstars.com.au 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

SEO Factors

blog.draftstars.com.au SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.draftstars.com.au 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 Blog.draftstars.com.au main page’s claimed encoding is iso-8859-1. 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

blog.draftstars.com.au

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