2.4 sec in total
41 ms
2.2 sec
181 ms
Click here to check amazing Unit4 content. Otherwise, check out these important facts you probably never knew about unit4.pt
We have many years’ experience of working with leading organizations across Portugal, both as an innovative, locally focused team and as a core part of Unit4’s global organization.
Visit unit4.ptWe analyzed Unit4.pt page load time and found that the first response time was 41 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
unit4.pt performance score
name
value
score
weighting
Value10.9 s
0/100
10%
Value20.0 s
0/100
25%
Value14.5 s
1/100
10%
Value5,000 ms
0/100
30%
Value0.082
94/100
15%
Value21.7 s
1/100
10%
41 ms
563 ms
26 ms
112 ms
101 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Unit4.pt, 42% (20 requests) were made to Unit4.com and 8% (4 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Unit4.com.
Page size can be reduced by 87.0 kB (23%)
381.8 kB
294.9 kB
In fact, the total size of Unit4.pt main page is 381.8 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. 70% of websites need less resources to load. Images take 137.5 kB which makes up the majority of the site volume.
Potential reduce by 86.7 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 86.7 kB or 83% of the original size.
Potential reduce by 0 B
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. Unit4 images are well optimized though.
Potential reduce by 105 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 129 B
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. Unit4.pt has all CSS files already compressed.
Number of requests can be reduced by 28 (74%)
38
10
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Unit4. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
unit4.pt
41 ms
portugal
563 ms
google_tag.script.js
26 ms
198047.js
112 ms
css
101 ms
style-cf.css
110 ms
css_6OSqPqRzH2P2QoahGhmt0IRm-Lfbh8sKOwWhPMogbYY.css
65 ms
css_eLLvlgBzNI6mA4xAOa3VL8O-Zfx85IgYDjxciQAMGUY.css
96 ms
email-decode.min.js
77 ms
js_PDHu9u178xyDKKmDf4rh-2WETEtw_9n_lNvuPV_0c1g.js
105 ms
ofi.min.js
107 ms
js_U8ZX_xqPTRPvTHsRNduRbGhqi7dz9xwDfkKxa5h_COA.js
107 ms
v652eace1692a40cfa3763df669d7439c1639079717194
330 ms
core.webeo.js
634 ms
nav-gradient-bkg-repeat.png
533 ms
hamburger.svg
67 ms
close.svg
68 ms
search-icon.svg
70 ms
close-icon-symbol.svg
71 ms
location_portugal_page_v200330.jpg.webp
781 ms
promo-background-graphic.svg
543 ms
ProximaNovaA-Regular.woff
470 ms
ProximaNovaA-Extrabld.woff
709 ms
icomoon.woff
861 ms
icomoon.ttf
49 ms
ProximaNovaA-Light.woff
780 ms
ProximaNovaA-Bold.woff
863 ms
ProximaNovaA-Semibold.woff
1056 ms
gtm.js
151 ms
js
194 ms
analytics.js
419 ms
web-vitals
416 ms
hotjar-477137.js
382 ms
otSDKStub.js
373 ms
ick9ctr5fut6.js
392 ms
collect
33 ms
collect
81 ms
collect
76 ms
f0ebb534-5bb6-4dca-b25e-9e2d10ce44eb.json
85 ms
modules.61e17720cf639c3e96a7.js
102 ms
web-vitals.iife.js
69 ms
ga-audiences
265 ms
collect
198 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
214 ms
otBannerSdk.js
196 ms
ga-audiences
67 ms
en.json
92 ms
nr-1216.min.js
87 ms
unit4.pt accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
unit4.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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
unit4.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unit4.pt 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 Unit4.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.
unit4.pt
Open Graph data is detected on the main page of Unit4. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: