4.1 sec in total
335 ms
3.6 sec
177 ms
Click here to check amazing Lovemail content. Otherwise, check out these important facts you probably never knew about lovemail.pt
Anúncios gratuitos, com possibilidade de publicar 9 fotos. Casas, carros, emprego, etc.
Visit lovemail.ptWe analyzed Lovemail.pt page load time and found that the first response time was 335 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lovemail.pt performance score
name
value
score
weighting
Value2.2 s
76/100
10%
Value3.5 s
64/100
25%
Value5.1 s
62/100
10%
Value670 ms
44/100
30%
Value0.035
100/100
15%
Value8.7 s
36/100
10%
335 ms
447 ms
327 ms
340 ms
222 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lovemail.pt, 75% (104 requests) were made to Ocasiao.pt and 5% (7 requests) were made to Cstatic.weborama.fr. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Ocasiao.pt.
Page size can be reduced by 476.2 kB (42%)
1.1 MB
649.0 kB
In fact, the total size of Lovemail.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. 40% of websites need less resources to load. Images take 538.5 kB which makes up the majority of the site volume.
Potential reduce by 146.4 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 146.4 kB or 86% of the original size.
Potential reduce by 30.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. Lovemail images are well optimized though.
Potential reduce by 180.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 180.1 kB or 67% of the original size.
Potential reduce by 119.3 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. Lovemail.pt needs all CSS files to be minified and compressed as it can save up to 119.3 kB or 82% of the original size.
Number of requests can be reduced by 35 (27%)
132
97
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lovemail. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
lovemail.pt
335 ms
www.ocasiao.pt
447 ms
css_ddd7f0166799e63aa12f467a1d095e39.css
327 ms
jquery.min.js
340 ms
drupal.js
222 ms
pt-pt_7e4769af0fb89d27902551a51eed40eb.js
222 ms
ajax_load.js
224 ms
apachesolr_autocomplete.js
230 ms
jquery.autocomplete.js
348 ms
fancy_login.js
349 ms
jquery.lazyload.js
350 ms
lightbox.js
351 ms
jquery.maskedinput-1.2.2.js
435 ms
uc_roles.js
440 ms
ocasiao_utils.js
439 ms
ajaxblocks.js
444 ms
script.js
445 ms
mlinks.js
459 ms
jbox.js
543 ms
gmg.top.header.bar.v3.js
346 ms
atrk.js
6 ms
conversion.js
35 ms
PbaSitetracker.js
453 ms
dc.js
45 ms
logo_ocasiao.png
115 ms
IN42807181.jpg
117 ms
IN31339449.jpg
116 ms
IN34794825.jpg
129 ms
IN42819726.jpg
114 ms
IN37324568.jpg
117 ms
IN41849676.jpg
231 ms
IN42328442.jpg
228 ms
IN34657519.png
229 ms
IN42751715.jpg
229 ms
IN42773980.jpg
228 ms
IN31523845.jpg
232 ms
IN42823199.jpg
340 ms
IN38186026.jpg
340 ms
IN42722846.jpg
338 ms
IN42087702.jpg
337 ms
IN42024645.jpg
341 ms
IN42827094.jpg
344 ms
IN41895624.jpg
446 ms
IN42826833.png
448 ms
IN42299776.jpg
451 ms
IN42770841.jpg
451 ms
IN36663782.jpg
452 ms
95244255_anuncio_0.jpg
458 ms
IN42391123.jpg
556 ms
IN41990067_0.jpg
567 ms
IN42762548.jpg
566 ms
IN31372134.jpg
567 ms
IN42770705.jpg
568 ms
IN37311756.jpg
572 ms
IN42605146.jpg
665 ms
IN32439018_0.jpg
667 ms
IN41813832.jpg
667 ms
IN40536235.jpg
667 ms
IN41930715.jpg
669 ms
globalMediaGroup.png
224 ms
css
22 ms
IN36582947.jpg
685 ms
homepage;pos=patrocinio;tile=6;dcopt=ist;sz=110x50;ord=3580424804240465
48 ms
gmgHeaderPlay.png
222 ms
klavika-medium-webfont.woff
511 ms
klavika-regular-webfont.woff
517 ms
__utm.gif
12 ms
IN42780340.png
665 ms
IN37943957.jpg
667 ms
IN31354352.jpg
668 ms
IN42323949.jpg
665 ms
atrk.gif
111 ms
netscope-gemius.js
527 ms
115 ms
IN31616681.jpg
659 ms
IN31334530.jpg
677 ms
products.js
123 ms
wfpd.min.js
130 ms
PbaSiteTracker.ashx
113 ms
test.png
246 ms
IN41934077.jpg
660 ms
IN42826873.jpg
664 ms
IN42374725.jpg
664 ms
IN42538809.jpg
665 ms
IN42353828.jpg
665 ms
IN39437249.jpg
690 ms
32 ms
comptage_wreport.fcgi
169 ms
external_all.html
29 ms
external_ids_sync.html
28 ms
external_libs.js
29 ms
ajaxblocks
1118 ms
IN42518551.jpg
663 ms
IN31586498.jpg
664 ms
IN42400633.jpg
663 ms
IN31517443.jpg
663 ms
IN31668435.jpg
692 ms
comptage_wreport.fcgi
170 ms
PbaSiteTracker.ashx
114 ms
dispatch.fcgi
171 ms
IN31379412.jpg
666 ms
IN40383443.jpg
664 ms
IN41999701.jpg
663 ms
IN42259675.jpg
662 ms
IN41770111.jpg
698 ms
IN38055157.jpg
763 ms
IN42035979.jpg
658 ms
IN31499643.jpg
657 ms
IN39397959.jpg
658 ms
IN42126555.jpg
697 ms
IN42773889.jpg
763 ms
IN42746510.jpg
760 ms
xlgemius.js
550 ms
IN42735690.jpg
669 ms
IN38096355.jpg
669 ms
IN42814853.jpg
712 ms
IN42773988.jpeg
774 ms
IN36524388.png
775 ms
IN41681786.jpg
758 ms
IN42688594.jpg
672 ms
IN42690915.jpg
718 ms
bt_destaque_DN.png
886 ms
bt_destaque_JN.png
885 ms
bt_destaque_relax_classificados.jpg
775 ms
banner_anuncie_ja.jpg
865 ms
transp.gif
28 ms
throbber.gif
677 ms
sprite_btn.png
722 ms
fita_destaque.png
777 ms
sprite1.png
1328 ms
ajax-loader_2.gif
949 ms
transp.gif
28 ms
grey.gif
855 ms
fpdata.js
110 ms
lsget.html
238 ms
controlinveste.png
304 ms
rexdot.js
111 ms
css_8e6eee9b90d54e29beabd134dd0dc9e2.css
112 ms
lovemail.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.
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.
lovemail.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
lovemail.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
Tap targets are not sized appropriately
EN
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lovemail.pt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Lovemail.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.
lovemail.pt
Open Graph description is not detected on the main page of Lovemail. 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: