Tools & Wizards About Us
tradesearch.co screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tradesearch.co

Book Online Trusted Professionals for Home maintenance & repair services Australia

Page Load Speed

9.1 sec in total

First Response

699 ms

Resources Loaded

6 sec

Page Rendered

2.4 sec

tradesearch.co screenshot

About Website

Welcome to tradesearch.co homepage info - get ready to check Tradesearch best content right away, or after learning these important things about tradesearch.co

Tradesearch Australia, a leading online platform for Home maintenance & repair services. We let you hire experts for your home repair services from our 100000+ trusted professionals in Australia.

Visit tradesearch.co

Key Findings

We analyzed Tradesearch.co page load time and found that the first response time was 699 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

tradesearch.co performance score

0

Network Requests Diagram

tradesearch.co

699 ms

www.tradesearch.co

1382 ms

reset.min.css

255 ms

style_homeNew.css

651 ms

slick.css

644 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 62% of them (34 requests) were addressed to the original Tradesearch.co, 13% (7 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Tradesearch.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 328.1 kB (63%)

Content Size

523.2 kB

After Optimization

195.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tradesearch.co main page is 523.2 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. 60% of websites need less resources to load. Javascripts take 251.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 46.7 kB

  • Original 55.8 kB
  • After minification 47.6 kB
  • After compression 9.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 8.2 kB, which is 15% 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 46.7 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 65.1 kB
  • After minification 65.1 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. Tradesearch images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 156.3 kB

  • Original 251.2 kB
  • After minification 243.0 kB
  • After compression 94.9 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 156.3 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 125.0 kB

  • Original 151.1 kB
  • After minification 127.7 kB
  • After compression 26.0 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. Tradesearch.co needs all CSS files to be minified and compressed as it can save up to 125.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (61%)

Requests Now

41

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tradesearch.co

tradesearch.co

699 ms

www.tradesearch.co

www.tradesearch.co

1382 ms

reset.min.css

reset.min.css

255 ms

style_homeNew.css

style_homeNew.css

651 ms

slick.css

slick.css

644 ms

animate.min.css

animate.min.css

646 ms

js

js

221 ms

js

js

251 ms

jquery.min.js

jquery.min.js

1041 ms

slick.js

slick.js

1039 ms

app_index.js

app_index.js

844 ms

customNew.js

customNew.js

837 ms

jquery.datetimepicker.full.js

jquery.datetimepicker.full.js

1232 ms

jquery.datetimepicker.css

jquery.datetimepicker.css

844 ms

conversion.js

conversion.js

258 ms

395 ms

font-awesome.css

font-awesome.css

594 ms

css

css

49 ms

css

css

62 ms

analytics.js

analytics.js

728 ms

fbevents.js

fbevents.js

878 ms

logo_new.png

logo_new.png

717 ms

banner-img.jpg

banner-img.jpg

855 ms

tell-us-what.png

tell-us-what.png

717 ms

network.png

network.png

699 ms

hire-the-right.png

hire-the-right.png

696 ms

make-better-img.png

make-better-img.png

2547 ms

default-user.png

default-user.png

832 ms

lapy_new_home.png

lapy_new_home.png

2098 ms

bottomLogo.png

bottomLogo.png

831 ms

location.png

location.png

617 ms

choose-service.png

choose-service.png

1566 ms

sprite.png

sprite.png

1974 ms

top-left-corner.png

top-left-corner.png

1566 ms

bottom-right-corner.png

bottom-right-corner.png

1568 ms

proximanova-light_0-webfont.woff

proximanova-light_0-webfont.woff

1481 ms

proximanova-reg_0-webfont.woff

proximanova-reg_0-webfont.woff

1465 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

244 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

246 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1056 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1072 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1071 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1071 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1072 ms

proximanova-bold_0-webfont.woff

proximanova-bold_0-webfont.woff

1463 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1651 ms

collect

collect

975 ms

346276145749371

346276145749371

1016 ms

left-arrow.png

left-arrow.png

854 ms

right-arrow.png

right-arrow.png

854 ms

511 ms

collect

collect

406 ms

240 ms

223 ms

ipinfo.io

ipinfo.io

94 ms

SEO Factors

tradesearch.co 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 Tradesearch.co 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 Tradesearch.co 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

tradesearch.co

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