13.6 sec in total
5.5 sec
7.9 sec
221 ms
Visit imoalk.com now to see the best up-to-date IMOALK content and also check out these interesting facts you probably never knew about imoalk.com
IMOALK Imobiliária by Christian Lima - Procura casa? Entre em contacto com a IMOALK Imobiliária by Christian Lima.
Visit imoalk.comWe analyzed Imoalk.com page load time and found that the first response time was 5.5 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
imoalk.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value7.8 s
3/100
25%
Value8.8 s
15/100
10%
Value4,970 ms
0/100
30%
Value1.314
1/100
15%
Value9.8 s
28/100
10%
5489 ms
106 ms
210 ms
212 ms
216 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 71% of them (75 requests) were addressed to the original Imoalk.com, 9% (10 requests) were made to Static.xx.fbcdn.net and 7% (7 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Imoalk.com.
Page size can be reduced by 1.3 MB (38%)
3.4 MB
2.1 MB
In fact, the total size of Imoalk.com main page is 3.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. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 84.2 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 84.2 kB or 84% of the original size.
Potential reduce by 86.0 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. IMOALK images are well optimized though.
Potential reduce by 876.3 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 876.3 kB or 75% of the original size.
Potential reduce by 229.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. Imoalk.com needs all CSS files to be minified and compressed as it can save up to 229.1 kB or 84% of the original size.
Number of requests can be reduced by 70 (69%)
102
32
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMOALK. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
imoalk.com
5489 ms
style.css
106 ms
language-selector.css
210 ms
mappress.css
212 ms
bootstrap.min.css
216 ms
bootstrap-responsive.min.css
210 ms
jquery-ui-1.11.4.custom.css
212 ms
mediaelementplayer.min.css
213 ms
wp-mediaelement.css
312 ms
wpv-pagination.css
313 ms
jquery.fancybox-1.3.7.min.css
314 ms
css
44 ms
css
58 ms
css
67 ms
css
67 ms
css
63 ms
css
69 ms
font-awesome.min.css
314 ms
css
67 ms
active-styles.css
314 ms
jquery.js
424 ms
jquery-migrate.min.js
412 ms
TweenMax.min.js
523 ms
ctaprofx.js
415 ms
ctapro.js
416 ms
jquery.min.js
47 ms
soliloquy.css
417 ms
wpv-compare.js
513 ms
bootstrap.min.js
519 ms
core.min.js
520 ms
datepicker.min.js
523 ms
underscore.min.js
526 ms
suggest.min.js
615 ms
main.js
624 ms
date.js
622 ms
mediaelement-and-player.min.js
629 ms
wp-mediaelement.js
626 ms
wp-util.min.js
629 ms
backbone.min.js
719 ms
wp-playlist.js
726 ms
wpv-pagination-embedded.js
904 ms
js
39 ms
jquery.wpvmap.js
729 ms
wp-embed.min.js
733 ms
sitepress.js
731 ms
js
93 ms
soliloquy-min.js
821 ms
style.css
738 ms
mappress.min.js
706 ms
jquery.fancybox-1.3.7.min.js
706 ms
jquery.easing.pack.js
705 ms
jquery.mousewheel.min.js
743 ms
html2canvas.js
854 ms
jspdf.debug.js
1061 ms
toBlob.js
643 ms
wp-emoji-release.min.js
127 ms
analytics.js
17 ms
LOGOTIPO-IMOALK.png
158 ms
en.png
159 ms
pt-pt.png
163 ms
fr.png
181 ms
130-1170x362_c.jpg
867 ms
212-1170x362_c.jpg
1119 ms
38-1170x362_c.jpg
1081 ms
410-1170x362_c.jpg
948 ms
511-1170x362_c.jpg
1317 ms
52-wpcf_328x145.jpg
558 ms
410-wpcf_328x145.jpg
671 ms
612-wpcf_328x145.jpg
802 ms
13-wpcf_328x145.jpg
882 ms
1-wpcf_328x145.jpg
971 ms
100-wpcf_328x145.jpg
985 ms
DownloadPhoto-1-wpcf_328x145.jpg
1051 ms
SAM_8439-wpcf_328x145.jpg
1074 ms
1-2-wpcf_328x145.jpg
1088 ms
LOGOTIPO-IMOALK-300x85.jpg
1156 ms
sdk.js
42 ms
collect
32 ms
1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf
26 ms
MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf
27 ms
fontawesome-webfont.woff
1237 ms
preloader.gif
1137 ms
left.png
1145 ms
right.png
1173 ms
circle.png
1212 ms
circle-hover.png
1244 ms
pause.png
1247 ms
play.png
1276 ms
video.png
1315 ms
33 ms
xd_arbiter.php
21 ms
xd_arbiter.php
30 ms
light-mask.png
944 ms
like_box.php
92 ms
kyEKgjk51ZE.css
37 ms
xgj7bXhJNEH.css
47 ms
q68gy-v_YMF.js
53 ms
FJmpeSpHpjS.js
81 ms
0wM5s1Khldu.js
35 ms
1bNoFZUdlYZ.js
34 ms
12072547_931694233588548_5907770418525710394_n.jpg
48 ms
10646618_738274946263812_9204986944796134035_n.jpg
11 ms
wL6VQj7Ab77.png
5 ms
s7jcwEQH7Sx.png
6 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
7 ms
imoalk.com 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 IDs are not unique
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
Form elements do not have associated labels
Links do not have a discernible name
imoalk.com 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
Page has valid source maps
imoalk.com SEO score
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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imoalk.com 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 Imoalk.com 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.
imoalk.com
Open Graph data is detected on the main page of IMOALK. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: