7 sec in total
354 ms
5 sec
1.6 sec
Click here to check amazing UZO content for Portugal. Otherwise, check out these important facts you probably never knew about uzo.pt
Uza já: Promoções em telemóveis, tarifários Uzo baratos de internet no telemóvel e chamadas a preços baixos em Portugal e internacionais. Paga só o que usas.
Visit uzo.ptWe analyzed Uzo.pt page load time and found that the first response time was 354 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Uzo.pt rating and web reputation
uzo.pt performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value18.4 s
0/100
25%
Value12.3 s
3/100
10%
Value1,740 ms
10/100
30%
Value0.399
25/100
15%
Value17.1 s
4/100
10%
354 ms
529 ms
512 ms
319 ms
557 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 51% of them (48 requests) were addressed to the original Uzo.pt, 27% (25 requests) were made to Static.xx.fbcdn.net and 9% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Insights.hotjar.com.
Page size can be reduced by 651.4 kB (61%)
1.1 MB
416.7 kB
In fact, the total size of Uzo.pt main page is 1.1 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. 65% of websites need less resources to load. Javascripts take 551.6 kB which makes up the majority of the site volume.
Potential reduce by 30.6 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 30.6 kB or 71% of the original size.
Potential reduce by 73.2 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. Obviously, UZO needs image optimization as it can save up to 73.2 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 384.8 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 384.8 kB or 70% of the original size.
Potential reduce by 162.8 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. Uzo.pt needs all CSS files to be minified and compressed as it can save up to 162.8 kB or 86% of the original size.
Number of requests can be reduced by 54 (61%)
88
34
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UZO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
uzo.pt
354 ms
pagina.uzo
529 ms
persistent_20100121.css
512 ms
Themepink_20100121_compressed.css
319 ms
jquery-1.7.1.min.js
557 ms
jquery.dimensions.min.js
223 ms
changeColor_20090529.min.js
325 ms
swfobject_20090529.min.js
302 ms
hpBanner.js
327 ms
google-analytics.js
404 ms
WebResource.axd
326 ms
ScriptResource.axd
593 ms
ScriptResource.axd
554 ms
netscope2.min.js
308 ms
cookies.js
356 ms
conversion.js
30 ms
bg_site1.gif
156 ms
analytics.js
33 ms
transp.gif
151 ms
img_sep_links_header.gif
152 ms
img_logo.gif
151 ms
img_sep_menu_header.gif
149 ms
1700213570_hl_PT_y50_1.png
391 ms
1700212533_hl_PT_malata_n402.png
390 ms
1700212534_hl_PT_ZTE_Blade_L3.png
392 ms
1700192834_hl_PT_Download.png
519 ms
1351.png
253 ms
img_sep_highlight.gif
360 ms
2017.jpg
453 ms
1969.gif
581 ms
1604.gif
479 ms
1979.gif
480 ms
2018.gif
438 ms
img_logo_footer.gif
503 ms
gtm.js
122 ms
collect
36 ms
collect
252 ms
bg_header.gif
269 ms
icon_arrow_navigator.gif
332 ms
bots.gif
332 ms
icons_arrows.gif
366 ms
img_balloon_big_left.gif
378 ms
bg_destaque.gif
379 ms
hotjar-32396.js
133 ms
impact-webfont.woff
267 ms
likebox.php
527 ms
bg_banner_item.png
222 ms
icon_more.gif
208 ms
comptage_wreport.fcgi
222 ms
ics_redes.gif
219 ms
cookies.css
223 ms
modules-f0126a45e2d0e5766f547aefbe0b8d9d.js
38 ms
comptage_wreport.fcgi
349 ms
close.dark.png
243 ms
228 ms
p_TUZUiNrjI.css
165 ms
CkaAj0ofVuQ.css
184 ms
XuwSaKdTuhR.css
207 ms
kgv-jfa46Fs.css
245 ms
zjrK3o-1DmV.css
269 ms
mm0vjjrXdxr.js
355 ms
Ta5YnQdNSFy.js
537 ms
XXn49zk5GnD.js
226 ms
OwNnuMlrnxQ.js
225 ms
9vSWWzdE5eF.js
695 ms
7ztEcde0Vs0.js
648 ms
n2oJSueYiMi.js
534 ms
XOfKJ6pUv0L.js
648 ms
rRqMEKuYkwU.js
534 ms
EEE2zYcQ4va.js
627 ms
Zp2gfEhcpC8.js
660 ms
d2Tdc2D6-_o.js
661 ms
X6hCdNrzbmL.js
660 ms
tsktgDt3YVI.js
662 ms
NZ1ljYgAVg4.js
661 ms
icon_open.gif
104 ms
impact-webfont.ttf
1187 ms
100 ms
visit-data
1910 ms
1012034_10156376679220722_2316768799492055833_n.jpg
1190 ms
484184_10152652931275722_1165518825_n.jpg
1269 ms
12650893_116158248769495_1786178260481035881_n.jpg
1265 ms
11219620_149851755376225_3545163967368605617_n.jpg
1286 ms
12647337_101463990239438_3297478718783055008_n.jpg
1264 ms
12728825_110428259346761_5853830216354195382_n.jpg
1292 ms
12009615_147413082269048_5934114806750327071_n.jpg
1275 ms
10603333_708403042563467_5082855150936204887_n.jpg
1255 ms
wL6VQj7Ab77.png
99 ms
s7jcwEQH7Sx.png
100 ms
print.css
1095 ms
kpVuqazI0LW.png
117 ms
wBg80dBy2Ra.js
146 ms
WIQcBxwlOXr.js
146 ms
bot_buy.gif
105 ms
uzo.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-*] attributes do not have valid values
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
uzo.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
uzo.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uzo.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 Uzo.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.
uzo.pt
Open Graph description is not detected on the main page of UZO. 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: