Tools & Wizards About Us
repo.net screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

repo.net

Repo.com | Repo.com | Online classifieds for used cars, trucks, and other vehicles

Page Load Speed

2.2 sec in total

First Response

356 ms

Resources Loaded

1.6 sec

Page Rendered

216 ms

repo.net screenshot

About Website

Visit repo.net now to see the best up-to-date Repo content and also check out these interesting facts you probably never knew about repo.net

Repo.com is an online classifieds solution for buying and selling bankrupt, repossessed and collected vehicles including used cars, trucks, vans, minivans, SUVs, and other vehicle repos in Burnaby and...

Visit repo.net

Key Findings

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

repo.net performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

repo.net

356 ms

www.repo.com

688 ms

gtm.js

75 ms

tf.js

51 ms

css

49 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Repo.net, 47% (28 requests) were made to Repo.com and 20% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (688 ms) relates to the external source Repo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.1 kB (8%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Repo.net main page is 1.4 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. 75% 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 996.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 41.0 kB

  • Original 52.2 kB
  • After minification 52.2 kB
  • After compression 11.2 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 41.0 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 23.2 kB

  • Original 996.0 kB
  • After minification 972.8 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. Repo images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 45.9 kB

  • Original 323.8 kB
  • After minification 323.8 kB
  • After compression 277.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 45.9 kB or 14% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 23.7 kB
  • After minification 23.7 kB
  • After compression 23.7 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. Repo.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (35%)

Requests Now

43

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

repo.net

repo.net

356 ms

www.repo.com

www.repo.com

688 ms

gtm.js

gtm.js

75 ms

tf.js

tf.js

51 ms

css

css

49 ms

89a69968b9.js

89a69968b9.js

93 ms

css2

css2

74 ms

15_72_header_8f26fcac.css

15_72_header_8f26fcac.css

40 ms

15_72_header_2ae4e3d5.js

15_72_header_2ae4e3d5.js

72 ms

tf.stage1.js

tf.stage1.js

3 ms

a58321fa-783d-466a-9d08-0304262b42e0

a58321fa-783d-466a-9d08-0304262b42e0

472 ms

carnow_plugin.js

carnow_plugin.js

211 ms

uLAjP8EUzneRGtdtZjbzQ.png

uLAjP8EUzneRGtdtZjbzQ.png

58 ms

dpRFOOsQcV4MZbddlYIV-Q.png

dpRFOOsQcV4MZbddlYIV-Q.png

57 ms

ca.gif

ca.gif

56 ms

us.gif

us.gif

93 ms

europeanunion.gif

europeanunion.gif

149 ms

gb.gif

gb.gif

152 ms

tfG-3ghpl933ES0jmJPQLA__h40.png

tfG-3ghpl933ES0jmJPQLA__h40.png

152 ms

Hq0Xqhe4HBJ1xCiMYWImDg.gif

Hq0Xqhe4HBJ1xCiMYWImDg.gif

152 ms

YwG0fnqrNof5et-82GbYjg.png

YwG0fnqrNof5et-82GbYjg.png

152 ms

tsJtrWd1-cRYkd-seZs-rg.png

tsJtrWd1-cRYkd-seZs-rg.png

218 ms

tYtkVtsyVvcpUIpEqu-Wjg.png

tYtkVtsyVvcpUIpEqu-Wjg.png

420 ms

3-lbjesjOh4rmieTNL-Xpw__w480.jpg

3-lbjesjOh4rmieTNL-Xpw__w480.jpg

217 ms

H1Oe8AONvxsUIgFCfgclBw__w480.jpg

H1Oe8AONvxsUIgFCfgclBw__w480.jpg

222 ms

OyvvhQVfL-e-ZMs-ZvNTqQ__w480.jpg

OyvvhQVfL-e-ZMs-ZvNTqQ__w480.jpg

221 ms

blPG-yzqJjy2GX3Vf80u4g__w480.jpg

blPG-yzqJjy2GX3Vf80u4g__w480.jpg

220 ms

L15RgHE6ZCy6lzgDCqOv-A__w480.jpg

L15RgHE6ZCy6lzgDCqOv-A__w480.jpg

336 ms

Ng1Uw8IRMToWZfSLgR1FPA__w480.jpg

Ng1Uw8IRMToWZfSLgR1FPA__w480.jpg

335 ms

uJWS1bdaZWRuUc57lHtgxg__w480.jpg

uJWS1bdaZWRuUc57lHtgxg__w480.jpg

334 ms

nhmq7DwXoogGs7bhQrcRxg__w480.jpg

nhmq7DwXoogGs7bhQrcRxg__w480.jpg

335 ms

destination

destination

140 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexaFRwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexaFRwaA.ttf

138 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNRwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNRwaA.ttf

139 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexc1RwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexc1RwaA.ttf

206 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexRNRwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexRNRwaA.ttf

224 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexU1WwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexU1WwaA.ttf

299 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexXRWwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexXRWwaA.ttf

225 ms

place

place

394 ms

js

js

215 ms

js

js

214 ms

piwik.js

piwik.js

582 ms

fbevents.js

fbevents.js

36 ms

15_72_footer_9f70470f.js

15_72_footer_9f70470f.js

287 ms

VDKs6-xHt7nL1pitXKlepg__w480.jpg

VDKs6-xHt7nL1pitXKlepg__w480.jpg

359 ms

d5whhptGu2I1FxmcztnCxg__w480.jpg

d5whhptGu2I1FxmcztnCxg__w480.jpg

360 ms

gzLZstC2p6-bIzX1O5fLHQ__w480.jpg

gzLZstC2p6-bIzX1O5fLHQ__w480.jpg

360 ms

5pO6igATNXrRa4LsYQBT3Q__w480.jpg

5pO6igATNXrRa4LsYQBT3Q__w480.jpg

357 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

228 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

155 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

155 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

173 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

173 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

224 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

226 ms

cn-client-z3-20240226110235.js.gz

cn-client-z3-20240226110235.js.gz

202 ms

loader.js

loader.js

52 ms

js

js

69 ms

call-tracking_7.js

call-tracking_7.js

4 ms

wcm

wcm

12 ms

Accessibility Review

repo.net accessibility score

64

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

repo.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

repo.net SEO score

83

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

High

Page is blocked from indexing

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

    N/A

  • Encoding

    UTF-8

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

repo.net

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