Tools & Wizards About Us
ptprime.pt screenshot

Report Summary

  • 0

    Performance

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ptprime.pt

MEO Empresas | Pacotes, Voz, Internet e Soluções TI/SI

Page Load Speed

7 sec in total

First Response

746 ms

Resources Loaded

6.2 sec

Page Rendered

87 ms

ptprime.pt screenshot

About Website

Visit ptprime.pt now to see the best up-to-date Ptprime content and also check out these interesting facts you probably never knew about ptprime.pt

Conheça os melhores pacotes, equipamentos e soluções de negócio para profissionais e PME. Esteja a par de campanhas e novidades para o seu negócio.

Visit ptprime.pt

Key Findings

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

Performance Metrics

ptprime.pt performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value30.2 s

0/100

25%

SI (Speed Index)

Value22.7 s

0/100

10%

TBT (Total Blocking Time)

Value5,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.918

0/100

15%

TTI (Time to Interactive)

Value32.1 s

0/100

10%

Network Requests Diagram

empresas

746 ms

QuantcastTag_MEO.js

630 ms

gtm.js

121 ms

ISites.Configurations.js

639 ms

searchv15.css

217 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ptprime.pt, 39% (34 requests) were made to Conteudos.meo.pt and 3% (3 requests) were made to Bywe3.byside.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Bywe3.byside.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 531.0 kB (37%)

Content Size

1.4 MB

After Optimization

918.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Ptprime.pt 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. Javascripts take 994.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 295.9 kB

  • Original 343.9 kB
  • After minification 333.5 kB
  • After compression 48.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 295.9 kB or 86% of the original size.

JavaScript Optimization

-20%

Potential reduce by 199.3 kB

  • Original 994.4 kB
  • After minification 994.4 kB
  • After compression 795.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 199.3 kB or 20% of the original size.

CSS Optimization

-32%

Potential reduce by 35.8 kB

  • Original 111.4 kB
  • After minification 111.4 kB
  • After compression 75.6 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. Ptprime.pt needs all CSS files to be minified and compressed as it can save up to 35.8 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (78%)

Requests Now

83

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

empresas

empresas

746 ms

QuantcastTag_MEO.js

QuantcastTag_MEO.js

630 ms

gtm.js

gtm.js

121 ms

ISites.Configurations.js

ISites.Configurations.js

639 ms

searchv15.css

searchv15.css

217 ms

initstrings.js

initstrings.js

343 ms

init.js

init.js

565 ms

ScriptResource.axd

ScriptResource.axd

496 ms

blank.js

blank.js

413 ms

ScriptResource.axd

ScriptResource.axd

420 ms

sp.res.js

sp.res.js

420 ms

sp.runtime.js

sp.runtime.js

444 ms

sp.init.js

sp.init.js

524 ms

sp.search.js

sp.search.js

519 ms

clientrenderer.js

clientrenderer.js

517 ms

srch.resources.js

srch.resources.js

541 ms

search.clientcontrols.js

search.clientcontrols.js

683 ms

search.cbs.js

search.cbs.js

612 ms

bootstrap.min.css

bootstrap.min.css

733 ms

theme.css

theme.css

859 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

741 ms

bootstrap.min.js

bootstrap.min.js

681 ms

system.js

system.js

807 ms

system.config.js

system.config.js

752 ms

functions.js

functions.js

751 ms

main.js

main.js

829 ms

brandlib.js

brandlib.js

924 ms

ISites.js

ISites.js

832 ms

ISites.Utils.js

ISites.Utils.js

833 ms

menuv5.js

menuv5.js

903 ms

postMessagesHelper.js

postMessagesHelper.js

910 ms

ISites.Taxonomy.js

ISites.Taxonomy.js

931 ms

ISites.ExtractPageCategory.js

ISites.ExtractPageCategory.js

925 ms

weglot.min.js

weglot.min.js

37 ms

ISites.WegLot.js

ISites.WegLot.js

939 ms

ISites.WegLot.Meo.js

ISites.WegLot.Meo.js

982 ms

byside_me.js

byside_me.js

1004 ms

bwc_we3.js

bwc_we3.js

197 ms

WebResource.axd

WebResource.axd

524 ms

system-polyfills.js

system-polyfills.js

148 ms

576 ms

Montserrat-Light.ttf

Montserrat-Light.ttf

211 ms

Montserrat-Regular.ttf

Montserrat-Regular.ttf

255 ms

Montserrat-SemiBold.ttf

Montserrat-SemiBold.ttf

219 ms

searchcenterurl

searchcenterurl

125 ms

strings.js

strings.js

190 ms

ProcessQuery

ProcessQuery

636 ms

ProcessQuery

ProcessQuery

648 ms

ProcessQuery

ProcessQuery

636 ms

ProcessQuery

ProcessQuery

895 ms

ProcessQuery

ProcessQuery

686 ms

ProcessQuery

ProcessQuery

770 ms

ProcessQuery

ProcessQuery

865 ms

ProcessQuery

ProcessQuery

992 ms

ProcessQuery

ProcessQuery

926 ms

ProcessQuery

ProcessQuery

983 ms

item_slideshow_card.js

item_slideshow_card.js

100 ms

group_content.js

group_content.js

97 ms

control_slideshow_cards.js

control_slideshow_cards.js

111 ms

item_quicklink.js

item_quicklink.js

110 ms

control_quicklinks.js

control_quicklinks.js

96 ms

item_multimedia.js

item_multimedia.js

191 ms

control_multimedia.js

control_multimedia.js

195 ms

item_mosaico.js

item_mosaico.js

188 ms

control_mosaico.js

control_mosaico.js

191 ms

item_colunas.js

item_colunas.js

193 ms

control_montra.js

control_montra.js

195 ms

item_links.js

item_links.js

279 ms

control_links.js

control_links.js

282 ms

menuv5.config.js

menuv5.config.js

106 ms

core.js

core.js

912 ms

customstrings.js

customstrings.js

817 ms

displaytemplateshelper.js

displaytemplateshelper.js

99 ms

GetTaxonomy

GetTaxonomy

478 ms

action.php

action.php

322 ms

main-menu-v5-ISites.js

main-menu-v5-ISites.js

192 ms

st.php

st.php

128 ms

usert_agent.php

usert_agent.php

1203 ms

slideshowCardsApp.min.js

slideshowCardsApp.min.js

106 ms

multimediaApp.min.js

multimediaApp.min.js

106 ms

montraApp.js

montraApp.js

96 ms

linksApp.min.js

linksApp.min.js

95 ms

mosaicApp.min.js

mosaicApp.min.js

104 ms

mquery.js

mquery.js

97 ms

sp.core.js

sp.core.js

101 ms

react.production.min.js

react.production.min.js

102 ms

react-dom.production.min.js

react-dom.production.min.js

104 ms

Accessibility Review

ptprime.pt accessibility score

59

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-*] attributes do not have valid values

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

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

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ptprime.pt SEO score

93

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

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

ptprime.pt

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