Tools & Wizards About Us
egor.pt screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

egor.pt

Página inicial - Egor

Page Load Speed

5.4 sec in total

First Response

516 ms

Resources Loaded

4.6 sec

Page Rendered

291 ms

egor.pt screenshot

About Website

Welcome to egor.pt homepage info - get ready to check Egor best content for Portugal right away, or after learning these important things about egor.pt

Conheça as nossas oportunidades de emprego e o que a Egor pode fazer pelo seu negócio. Conheça as nossas soluções de Recursos Humanos.

Visit egor.pt

Key Findings

We analyzed Egor.pt page load time and found that the first response time was 516 ms and then it took 4.9 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

egor.pt performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

516 ms

templates.uber.less.bootstrap.less.css

422 ms

jcemediabox.css

217 ms

style.css

217 ms

system.css

223 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 88% of them (66 requests) were addressed to the original Egor.pt, 5% (4 requests) were made to S7.addthis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Egor.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (18%)

Content Size

8.0 MB

After Optimization

6.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Egor.pt main page is 8.0 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 6.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 121.2 kB

  • Original 156.2 kB
  • After minification 152.9 kB
  • After compression 35.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 121.2 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 32.1 kB

  • Original 6.2 MB
  • After minification 6.1 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. Egor images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 712.0 kB

  • Original 1.0 MB
  • After minification 953.4 kB
  • After compression 302.4 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 712.0 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 549.4 kB

  • Original 638.9 kB
  • After minification 555.6 kB
  • After compression 89.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. Egor.pt needs all CSS files to be minified and compressed as it can save up to 549.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (80%)

Requests Now

71

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Egor. 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 36 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

516 ms

templates.uber.less.bootstrap.less.css

templates.uber.less.bootstrap.less.css

422 ms

jcemediabox.css

jcemediabox.css

217 ms

style.css

style.css

217 ms

system.css

system.css

223 ms

plugins.system.t3.base-bs3.less.legacy-grid.less.css

plugins.system.t3.base-bs3.less.legacy-grid.less.css

222 ms

font-awesome.css

font-awesome.css

340 ms

plugins.system.t3.base-bs3.less.t3.less.css

plugins.system.t3.base-bs3.less.t3.less.css

322 ms

templates.uber.less.core.less.css

templates.uber.less.core.less.css

323 ms

templates.uber.less.typography.less.css

templates.uber.less.typography.less.css

333 ms

templates.uber.less.forms.less.css

templates.uber.less.forms.less.css

335 ms

templates.uber.less.navigation.less.css

templates.uber.less.navigation.less.css

433 ms

templates.uber.less.navbar.less.css

templates.uber.less.navbar.less.css

433 ms

templates.uber.less.modules.less.css

templates.uber.less.modules.less.css

443 ms

templates.uber.less.joomla.less.css

templates.uber.less.joomla.less.css

554 ms

templates.uber.less.components.less.css

templates.uber.less.components.less.css

448 ms

templates.uber.less.style.less.css

templates.uber.less.style.less.css

524 ms

templates.uber.less.layouts.blog.less.css

templates.uber.less.layouts.blog.less.css

531 ms

templates.uber.less.extras.com_virtuemart.less.css

templates.uber.less.extras.com_virtuemart.less.css

642 ms

plugins.system.t3.base-bs3.less.megamenu.less.css

plugins.system.t3.base-bs3.less.megamenu.less.css

560 ms

templates.uber.less.megamenu.less.css

templates.uber.less.megamenu.less.css

629 ms

plugins.system.t3.base-bs3.less.off-canvas.less.css

plugins.system.t3.base-bs3.less.off-canvas.less.css

636 ms

templates.uber.less.off-canvas.less.css

templates.uber.less.off-canvas.less.css

661 ms

font-awesome.min.css

font-awesome.min.css

662 ms

styles.css

styles.css

665 ms

styles.css

styles.css

733 ms

styles.css

styles.css

741 ms

styles.css

styles.css

747 ms

styles.css

styles.css

770 ms

styles.css

styles.css

770 ms

custom.css

custom.css

776 ms

custom_default-homepage.css

custom_default-homepage.css

836 ms

templates.uber.less.layouts.docs.less.css

templates.uber.less.layouts.docs.less.css

847 ms

template.css

template.css

853 ms

templates.uber.acm.bar.less.style.less.css

templates.uber.acm.bar.less.style.less.css

879 ms

addthis_widget.js

addthis_widget.js

9 ms

templates.uber.acm.header.less.style.less.css

templates.uber.acm.header.less.style.less.css

796 ms

jquery.min.js

jquery.min.js

909 ms

jquery-noconflict.js

jquery-noconflict.js

738 ms

system.css

system.css

742 ms

jquery-migrate.min.js

jquery-migrate.min.js

752 ms

caption.js

caption.js

679 ms

jcemediabox.js

jcemediabox.js

791 ms

bootstrap.js

bootstrap.js

724 ms

jquery.tap.min.js

jquery.tap.min.js

733 ms

off-canvas.js

off-canvas.js

736 ms

script.js

script.js

679 ms

menu.js

menu.js

733 ms

jquery.inview.min.js

jquery.inview.min.js

741 ms

jquery.parallax-1.1.3.js

jquery.parallax-1.1.3.js

739 ms

jquery.placeholder.js

jquery.placeholder.js

772 ms

script.js

script.js

698 ms

mootools-core.js

mootools-core.js

819 ms

core.js

core.js

719 ms

script.js

script.js

728 ms

nav-collapse.js

nav-collapse.js

702 ms

analytics.js

analytics.js

64 ms

logo_egor_central_334.png

logo_egor_central_334.png

145 ms

logo_egor.png

logo_egor.png

148 ms

en.gif

en.gif

146 ms

StoneSansStd-Medium.otf

StoneSansStd-Medium.otf

261 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

537 ms

popup.html

popup.html

183 ms

tooltip.html

tooltip.html

185 ms

300lo.json

300lo.json

36 ms

background_homepage_left_1920.png

background_homepage_left_1920.png

2159 ms

background_homepage_right_1920.png

background_homepage_right_1920.png

2165 ms

homepage_ie_pessoas_1920.png

homepage_ie_pessoas_1920.png

1768 ms

homepage_ie_negocios_1920.png

homepage_ie_negocios_1920.png

2019 ms

collect

collect

13 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

36 ms

layers.3643cb2e25fb91c29386.js

layers.3643cb2e25fb91c29386.js

34 ms

collect

collect

145 ms

pt.js

pt.js

21 ms

ga-audiences

ga-audiences

39 ms

Accessibility Review

egor.pt accessibility score

90

Accessibility Issues

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

Links do not have a discernible name

Best Practices

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

egor.pt SEO score

100

Search Engine Optimization Advices

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

egor.pt

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