Tools & Wizards About Us
rarespares.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

rarespares.net

rarespares.net

Page Load Speed

18.2 sec in total

First Response

309 ms

Resources Loaded

17.7 sec

Page Rendered

186 ms

rarespares.net screenshot

About Website

Welcome to rarespares.net homepage info - get ready to check Rarespares best content right away, or after learning these important things about rarespares.net

This domain may be for sale!

Visit rarespares.net

Key Findings

We analyzed Rarespares.net page load time and found that the first response time was 309 ms and then it took 17.9 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

rarespares.net performance score

0

Network Requests Diagram

index.php

309 ms

index.php

438 ms

scripts.js

4172 ms

reset-fonts-grids.css

367 ms

style.css

468 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rarespares.net, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (10.8 sec) relates to the external source 123-parking.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.0 kB (46%)

Content Size

262.7 kB

After Optimization

142.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rarespares.net main page is 262.7 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. Only 10% of websites need less resources to load. Javascripts take 131.0 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 5.8 kB

  • Original 8.1 kB
  • After minification 7.1 kB
  • After compression 2.4 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 1.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 5.8 kB or 71% of the original size.

Image Optimization

-2%

Potential reduce by 1.6 kB

  • Original 102.0 kB
  • After minification 100.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. Rarespares images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 95.5 kB

  • Original 131.0 kB
  • After minification 95.5 kB
  • After compression 35.4 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 95.5 kB or 73% of the original size.

CSS Optimization

-79%

Potential reduce by 17.2 kB

  • Original 21.6 kB
  • After minification 16.5 kB
  • After compression 4.4 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. Rarespares.net needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (52%)

Requests Now

27

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index.php

index.php

309 ms

index.php

index.php

438 ms

scripts.js

scripts.js

4172 ms

reset-fonts-grids.css

reset-fonts-grids.css

367 ms

style.css

style.css

468 ms

prototype.js

prototype.js

629 ms

scriptaculous.js

scriptaculous.js

279 ms

lightbox.js

lightbox.js

10790 ms

lightbox.css

lightbox.css

508 ms

effects.js

effects.js

652 ms

top.gif

top.gif

277 ms

123-reg-logo2.png

123-reg-logo2.png

275 ms

login.gif

login.gif

277 ms

blue-submit.gif

blue-submit.gif

276 ms

home-main.gif

home-main.gif

278 ms

home-main-make-money-sleep.jpg

home-main-make-money-sleep.jpg

805 ms

nav.gif

nav.gif

1771 ms

side.gif

side.gif

559 ms

errors_grad.png

errors_grad.png

1769 ms

main.gif

main.gif

1765 ms

green-arrow.gif

green-arrow.gif

1772 ms

b1.gif

b1.gif

809 ms

b2.gif

b2.gif

2016 ms

b3.gif

b3.gif

2022 ms

b4.gif

b4.gif

2041 ms

ga.js

ga.js

178 ms

__utm.gif

__utm.gif

56 ms

loading.gif

loading.gif

346 ms

closelabel.gif

closelabel.gif

590 ms

SEO Factors

rarespares.net SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rarespares.net 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 Rarespares.net 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

rarespares.net

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