Tools & Wizards About Us
cargeni.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

cargeni.com

Cargeni.com | The Car Search Engine

Page Load Speed

3.5 sec in total

First Response

51 ms

Resources Loaded

3.1 sec

Page Rendered

319 ms

cargeni.com screenshot

About Website

Visit cargeni.com now to see the best up-to-date Cargeni content and also check out these interesting facts you probably never knew about cargeni.com

Cargeni.com The Car Search Engine for Used Cars and Trucks classifieds for Sale

Visit cargeni.com

Key Findings

We analyzed Cargeni.com page load time and found that the first response time was 51 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

cargeni.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value1,360 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.393

26/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

cargeni.com

51 ms

cargeni.com

61 ms

www.cargeni.com

48 ms

www.cargeni.com

405 ms

flatly.css

60 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 17% of them (15 requests) were addressed to the original Cargeni.com, 27% (24 requests) were made to I.ebayimg.com and 10% (9 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Epnt.ebay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 214.5 kB (16%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cargeni.com 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. 60% of websites need less resources to load. Images take 658.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 44.9 kB

  • Original 57.2 kB
  • After minification 56.0 kB
  • After compression 12.3 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 44.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 19 B

  • Original 658.0 kB
  • After minification 657.9 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. Cargeni images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 165.3 kB

  • Original 601.4 kB
  • After minification 601.1 kB
  • After compression 436.1 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 165.3 kB or 27% of the original size.

CSS Optimization

-6%

Potential reduce by 4.3 kB

  • Original 66.4 kB
  • After minification 66.4 kB
  • After compression 62.1 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. Cargeni.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (45%)

Requests Now

73

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cargeni.com

cargeni.com

51 ms

cargeni.com

cargeni.com

61 ms

www.cargeni.com

www.cargeni.com

48 ms

www.cargeni.com

www.cargeni.com

405 ms

flatly.css

flatly.css

60 ms

jquery.fancybox.css

jquery.fancybox.css

27 ms

docs.css

docs.css

79 ms

app.css

app.css

24 ms

font-awesome.css

font-awesome.css

112 ms

s-l140.jpg

s-l140.jpg

35 ms

US.png

US.png

68 ms

Canada.png

Canada.png

66 ms

mclaren-sports-cars.jpg

mclaren-sports-cars.jpg

43 ms

bmw-cars.jpg

bmw-cars.jpg

44 ms

s-l140.jpg

s-l140.jpg

38 ms

1

1

324 ms

rocket-loader.min.js

rocket-loader.min.js

47 ms

s-l140.jpg

s-l140.jpg

45 ms

s-l140.jpg

s-l140.jpg

45 ms

s-l140.jpg

s-l140.jpg

46 ms

s-l140.jpg

s-l140.jpg

50 ms

s-l140.jpg

s-l140.jpg

63 ms

s-l140.jpg

s-l140.jpg

50 ms

s-l140.jpg

s-l140.jpg

50 ms

s-l140.jpg

s-l140.jpg

51 ms

s-l140.jpg

s-l140.jpg

52 ms

s-l140.jpg

s-l140.jpg

66 ms

s-l140.jpg

s-l140.jpg

53 ms

s-l140.jpg

s-l140.jpg

51 ms

s-l140.jpg

s-l140.jpg

68 ms

s-l140.jpg

s-l140.jpg

53 ms

s-l140.jpg

s-l140.jpg

59 ms

s-l140.jpg

s-l140.jpg

60 ms

s-l140.jpg

s-l140.jpg

60 ms

s-l140.jpg

s-l140.jpg

68 ms

s-l140.jpg

s-l140.jpg

76 ms

s-l140.jpg

s-l140.jpg

60 ms

s-l140.jpg

s-l140.jpg

61 ms

s-l140.jpg

s-l140.jpg

62 ms

css

css

30 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

17 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

25 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

10 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

52 ms

adsbygoogle.js

adsbygoogle.js

113 ms

epn-smart-tools.js

epn-smart-tools.js

1167 ms

show_ads_impl.js

show_ads_impl.js

230 ms

zrt_lookup.html

zrt_lookup.html

34 ms

ads

ads

496 ms

sodar

sodar

79 ms

sodar2.js

sodar2.js

18 ms

runner.html

runner.html

8 ms

aframe

aframe

35 ms

q3_ozqIbHCwHEmDedgzG-D6UnUyzi2L496FFdqoLokA.js

q3_ozqIbHCwHEmDedgzG-D6UnUyzi2L496FFdqoLokA.js

3 ms

reactive_library.js

reactive_library.js

152 ms

ca-pub-6630109012927307

ca-pub-6630109012927307

60 ms

ads

ads

242 ms

ads

ads

236 ms

15682828423183201445

15682828423183201445

12 ms

load_preloaded_resource.js

load_preloaded_resource.js

18 ms

abg_lite.js

abg_lite.js

29 ms

window_focus.js

window_focus.js

134 ms

qs_click_protection.js

qs_click_protection.js

34 ms

ufs_web_display.js

ufs_web_display.js

27 ms

bbae3fd3506d8d9338f85d10ea9db8af.js

bbae3fd3506d8d9338f85d10ea9db8af.js

161 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

130 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

134 ms

icon.png

icon.png

135 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

163 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

166 ms

js

js

211 ms

nmedianet.js

nmedianet.js

180 ms

css

css

35 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

5 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

9 ms

bping.php

bping.php

256 ms

SAFEFRAME.html

SAFEFRAME.html

328 ms

videoAds.js

videoAds.js

385 ms

q

q

40 ms

sa30O7WeJNzu8x7oKdCcujxNj08-gvZudrea3FT7Uzc.js

sa30O7WeJNzu8x7oKdCcujxNj08-gvZudrea3FT7Uzc.js

42 ms

SAFEFRAME.html

SAFEFRAME.html

336 ms

onejs

onejs

144 ms

bping.php

bping.php

14 ms

q

q

1 ms

jquery-2.0.0.min.js

jquery-2.0.0.min.js

15 ms

jquery.fancybox.js

jquery.fancybox.js

577 ms

bql.php

bql.php

44 ms

Roboto-Bold.woff

Roboto-Bold.woff

5 ms

bql.php

bql.php

19 ms

Accessibility Review

cargeni.com accessibility score

79

Accessibility Issues

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.

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

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

cargeni.com best practices score

67

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

High

Page has valid source maps

SEO Factors

cargeni.com SEO score

85

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

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 Cargeni.com 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 Cargeni.com 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

cargeni.com

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