Tools & Wizards About Us
elpe.pt screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    50% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

elpe.pt

Electropescador - 33 anos de relação única com o cliente.

Page Load Speed

3.7 sec in total

First Response

791 ms

Resources Loaded

2.7 sec

Page Rendered

207 ms

elpe.pt screenshot

About Website

Click here to check amazing Elpe content for Portugal. Otherwise, check out these important facts you probably never knew about elpe.pt

Somos uma empresa familiar portuguesa. Vendemos diversos produtos desde: Electrodomésticos, telemóveis, material eléctrico e muito mais.

Visit elpe.pt

Key Findings

We analyzed Elpe.pt page load time and found that the first response time was 791 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

elpe.pt performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value27.4 s

0/100

10%

TBT (Total Blocking Time)

Value32,120 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value52.2 s

0/100

10%

Network Requests Diagram

elpe.pt

791 ms

stylesheet.css

525 ms

popupmod.js

513 ms

jquery-1.4.min.js

628 ms

loopedslider.min.js

536 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 97% of them (56 requests) were addressed to the original Elpe.pt, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Elpe.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.6 kB (27%)

Content Size

504.2 kB

After Optimization

368.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Elpe.pt main page is 504.2 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. 30% of websites need less resources to load. Images take 323.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 56.9 kB

  • Original 65.9 kB
  • After minification 63.0 kB
  • After compression 9.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. 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 56.9 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 9.7 kB

  • Original 323.7 kB
  • After minification 314.0 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. Elpe images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 51.3 kB

  • Original 93.5 kB
  • After minification 93.2 kB
  • After compression 42.2 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 51.3 kB or 55% of the original size.

CSS Optimization

-83%

Potential reduce by 17.6 kB

  • Original 21.1 kB
  • After minification 17.2 kB
  • After compression 3.5 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. Elpe.pt needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (49%)

Requests Now

55

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

elpe.pt

elpe.pt

791 ms

stylesheet.css

stylesheet.css

525 ms

popupmod.js

popupmod.js

513 ms

jquery-1.4.min.js

jquery-1.4.min.js

628 ms

loopedslider.min.js

loopedslider.min.js

536 ms

logo6.gif

logo6.gif

128 ms

bannertopo497x90px.jpg

bannertopo497x90px.jpg

254 ms

logoprincipal.jpg

logoprincipal.jpg

106 ms

logo7.gif

logo7.gif

105 ms

inicio.jpg

inicio.jpg

414 ms

novos.jpg

novos.jpg

413 ms

minhaconta.jpg

minhaconta.jpg

210 ms

carrinho.jpg

carrinho.jpg

210 ms

checkout.jpg

checkout.jpg

231 ms

corner_right_left.gif

corner_right_left.gif

313 ms

corner_left.gif

corner_left.gif

314 ms

corner_right.gif

corner_right.gif

339 ms

pixel_trans.gif

pixel_trans.gif

357 ms

m18.gif

m18.gif

425 ms

m25.jpg

m25.jpg

427 ms

m20.gif

m20.gif

449 ms

corner_right_left.gif

corner_right_left.gif

479 ms

corner_left.gif

corner_left.gif

514 ms

corner_right.gif

corner_right.gif

516 ms

corner_right_left.gif

corner_right_left.gif

526 ms

corner_left.gif

corner_left.gif

530 ms

corner_right.gif

corner_right.gif

552 ms

corner_right_left.gif

corner_right_left.gif

582 ms

corner_left.gif

corner_left.gif

618 ms

corner_right.gif

corner_right.gif

619 ms

banerrotativo12_500x140px.jpg

banerrotativo12_500x140px.jpg

732 ms

melhorpreco.jpg

melhorpreco.jpg

640 ms

pecas_e_acessorios.png

pecas_e_acessorios.png

1001 ms

ax700pt.jpg

ax700pt.jpg

686 ms

+info.jpg

+info.jpg

722 ms

adicar.jpg

adicar.jpg

722 ms

nopic.jpg

nopic.jpg

745 ms

aquosphone.jpg

aquosphone.jpg

894 ms

blush810br.png

blush810br.png

1031 ms

d3azul.jpg

d3azul.jpg

825 ms

corner_left.gif

corner_left.gif

818 ms

ga.js

ga.js

12 ms

__utm.gif

__utm.gif

11 ms

corner_right.gif

corner_right.gif

749 ms

button_quick_find.gif

button_quick_find.gif

832 ms

m200.gif

m200.gif

817 ms

iframe.png

iframe.png

749 ms

corner_left.gif

corner_left.gif

794 ms

corner_right.gif

corner_right.gif

813 ms

corner_left.gif

corner_left.gif

798 ms

corner_right.gif

corner_right.gif

749 ms

right_banner190xsemlimitepx.jpg

right_banner190xsemlimitepx.jpg

794 ms

padlock.png

padlock.png

770 ms

m31.gif

m31.gif

782 ms

m25.gif

m25.gif

737 ms

corner_right_left.gif

corner_right_left.gif

739 ms

corner_right_left.gif

corner_right_left.gif

742 ms

corner_right_left.gif

corner_right_left.gif

785 ms

Accessibility Review

elpe.pt accessibility score

87

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

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

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

elpe.pt 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

elpe.pt SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    PT

  • Language Claimed

    PT

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elpe.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Elpe.pt 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

elpe.pt

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