Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

en.telepecas.com

TelePeças | Online platform for sale used auto parts

Page Load Speed

5 sec in total

First Response

297 ms

Resources Loaded

4.1 sec

Page Rendered

612 ms

en.telepecas.com screenshot

About Website

Click here to check amazing En Tele Pecas content for Portugal. Otherwise, check out these important facts you probably never knew about en.telepecas.com

Search and compare used auto parts you are looking for from over 250 validated suppliers. Save time and money. Order them now!

Visit en.telepecas.com

Key Findings

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

Performance Metrics

en.telepecas.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value4,800 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.14

79/100

15%

TTI (Time to Interactive)

Value29.0 s

0/100

10%

Network Requests Diagram

en.telepecas.com

297 ms

en.telepecas.com

789 ms

bootstrap.min.css

94 ms

bootstrap-responsive.min.css

184 ms

style.css

277 ms

Our browser made a total of 147 requests to load all elements on the main page. We found that 52% of them (77 requests) were addressed to the original En.telepecas.com, 21% (31 requests) were made to Pt.telepecas.com and 3% (5 requests) were made to S3.eu-central-1.wasabisys.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Pt.telepecas.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.9 MB (33%)

Content Size

8.8 MB

After Optimization

5.9 MB

In fact, the total size of En.telepecas.com main page is 8.8 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. 85% 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 7.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 256.8 kB

  • Original 297.1 kB
  • After minification 218.9 kB
  • After compression 40.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. This page needs HTML code to be minified as it can gain 78.2 kB, which is 26% 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 256.8 kB or 86% of the original size.

Image Optimization

-32%

Potential reduce by 2.3 MB

  • Original 7.1 MB
  • After minification 4.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. Obviously, En Tele Pecas needs image optimization as it can save up to 2.3 MB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 328.6 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 897.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 328.6 kB or 27% of the original size.

CSS Optimization

-27%

Potential reduce by 44.8 kB

  • Original 163.2 kB
  • After minification 135.5 kB
  • After compression 118.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. En.telepecas.com needs all CSS files to be minified and compressed as it can save up to 44.8 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (51%)

Requests Now

140

After Optimization

68

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

Accessibility Review

en.telepecas.com accessibility score

76

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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 IDs are not unique

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

Links do not have a discernible name

Best Practices

en.telepecas.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

en.telepecas.com SEO score

82

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise En.telepecas.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 En.telepecas.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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