Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

pepecar.com

Cheap car hire specialized in Spain and UK | Pepecar

Page Load Speed

13.6 sec in total

First Response

400 ms

Resources Loaded

9.3 sec

Page Rendered

3.9 sec

pepecar.com screenshot

About Website

Welcome to pepecar.com homepage info - get ready to check Pepecar best content for Spain right away, or after learning these important things about pepecar.com

The best prices on Car Rental you have in Pepecar. Reserve now your Car Rental in hundreds of destinations in Spain.

Visit pepecar.com

Key Findings

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

Performance Metrics

pepecar.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value17,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.531

14/100

15%

TTI (Time to Interactive)

Value25.9 s

0/100

10%

Network Requests Diagram

pepecar.com

400 ms

www.pepecar.com

312 ms

www.pepecar.com

758 ms

css

345 ms

css

355 ms

Our browser made a total of 254 requests to load all elements on the main page. We found that 97% of them (246 requests) were addressed to the original Pepecar.com, 1% (2 requests) were made to Fonts.googleapis.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Pepecar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (39%)

Content Size

3.3 MB

After Optimization

2.1 MB

In fact, the total size of Pepecar.com main page is 3.3 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. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 164.1 kB

  • Original 184.1 kB
  • After minification 155.4 kB
  • After compression 20.0 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 28.6 kB, which is 16% 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 164.1 kB or 89% of the original size.

Image Optimization

-8%

Potential reduce by 160.2 kB

  • Original 1.9 MB
  • After minification 1.8 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. Pepecar images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 668.3 kB

  • Original 889.8 kB
  • After minification 681.7 kB
  • After compression 221.5 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 668.3 kB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 296.7 kB

  • Original 354.6 kB
  • After minification 344.2 kB
  • After compression 58.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. Pepecar.com needs all CSS files to be minified and compressed as it can save up to 296.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 207 (84%)

Requests Now

247

After Optimization

40

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

Accessibility Review

pepecar.com accessibility score

80

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pepecar.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pepecar.com SEO score

86

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 Pepecar.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 Pepecar.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

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