3.8 sec in total
1.1 sec
2.6 sec
166 ms
Welcome to log.pt homepage info - get ready to check Log best content right away, or after learning these important things about log.pt
A sua equipa de desenvolvimento de software ágil.
Visit log.ptWe analyzed Log.pt page load time and found that the first response time was 1.1 sec and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
log.pt performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.1 s
76/100
25%
Value7.3 s
28/100
10%
Value140 ms
95/100
30%
Value0.004
100/100
15%
Value4.6 s
81/100
10%
1053 ms
485 ms
25 ms
35 ms
44 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 49% of them (18 requests) were addressed to the original Log.pt, 30% (11 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to 30f7ou26svq02syn9yxj6fs2.wpengine.netdna-cdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Log.pt.
Page size can be reduced by 633.3 kB (55%)
1.2 MB
528.5 kB
In fact, the total size of Log.pt main page is 1.2 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. 55% of websites need less resources to load. CSS take 404.9 kB which makes up the majority of the site volume.
Potential reduce by 10.1 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 1.6 kB, which is 12% 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 10.1 kB or 74% of the original size.
Potential reduce by 13.5 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. Log images are well optimized though.
Potential reduce by 254.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 254.5 kB or 71% of the original size.
Potential reduce by 355.1 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. Log.pt needs all CSS files to be minified and compressed as it can save up to 355.1 kB or 88% of the original size.
Number of requests can be reduced by 8 (33%)
24
16
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Log. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
log.pt
1053 ms
autoptimize_37d199864843380b754cc4eaa2479746.css
485 ms
css
25 ms
css
35 ms
css
44 ms
autoptimize_d8671f1da134d9f2cda0daa99982aa8b.js
415 ms
analytics.js
59 ms
background7.jpg
726 ms
logo.png
329 ms
fb.png
336 ms
tw.png
338 ms
inst.png
341 ms
github.png
345 ms
wp.png
399 ms
logo-adv.png
405 ms
ericsson-logo.png
407 ms
logo-nos.png
408 ms
logo-pt.png
414 ms
logo-sapo.png
469 ms
logo-sonae.png
475 ms
logo-worten.png
477 ms
vodafone-logo.png
478 ms
logo.png
161 ms
wp-emoji-release.min.js
91 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
12 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
14 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
12 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
13 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
29 ms
QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf
29 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
29 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
53 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
54 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
58 ms
4cKlrioa77J2iqTqBgkRWg.ttf
58 ms
collect
44 ms
ETmodules_v2_4.ttf
277 ms
log.pt accessibility score
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
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Links do not have a discernible name
log.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
log.pt SEO score
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
Document uses legible font sizes
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Log.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Log.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.
log.pt
Open Graph description is not detected on the main page of Log. 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: