8.2 sec in total
974 ms
3.8 sec
3.4 sec
Visit whanse.com now to see the best up-to-date W Hanse content and also check out these interesting facts you probably never knew about whanse.com
Imóveis para alugar e vender em Campo Mourão e Região você encontra na W Hanse Imóveis, o melhor negócio para a sua família.
Visit whanse.comWe analyzed Whanse.com page load time and found that the first response time was 974 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
whanse.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value11.2 s
0/100
25%
Value15.2 s
1/100
10%
Value8,670 ms
0/100
30%
Value0.28
43/100
15%
Value21.2 s
1/100
10%
974 ms
111 ms
146 ms
174 ms
173 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whanse.com, 8% (8 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (974 ms) relates to the external source Whanse.com.br.
Page size can be reduced by 219.8 kB (9%)
2.4 MB
2.2 MB
In fact, the total size of Whanse.com main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 102.3 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 102.3 kB or 86% of the original size.
Potential reduce by 110.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. W Hanse images are well optimized though.
Potential reduce by 4.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Whanse.com has all CSS files already compressed.
Number of requests can be reduced by 52 (63%)
83
31
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of W Hanse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
www.whanse.com.br
974 ms
wp-emoji-release.min.js
111 ms
toolkit.css
146 ms
bt-social.css
174 ms
styles.css
173 ms
cookie-law-info-public.css
169 ms
cookie-law-info-gdpr.css
161 ms
style.css
215 ms
style.css
227 ms
sow-cta-default-2d71aa25d7bc.css
228 ms
sow-image-default-17bc2272b535.css
206 ms
style.css
205 ms
sow-features-default-31a204a365d4.css
222 ms
slider.css
247 ms
sow-slider-default-53fd0f98de19.css
225 ms
sow-social-media-buttons-atom-2d98b9b28e9f.css
262 ms
sow-image-default-d6014b76747a.css
260 ms
sunflower.css
311 ms
all.css
255 ms
font-awesome.css
308 ms
style.css
294 ms
gallery.css
289 ms
css
223 ms
jquery.js
289 ms
jquery-migrate.min.js
350 ms
jquery.easing.js
373 ms
modernizr.js
395 ms
jquery.jplayer.min.js
395 ms
cookie-law-info-public.js
394 ms
cta.min.js
430 ms
jquery.cycle.min.js
497 ms
jquery.slider.min.js
396 ms
js
429 ms
jquery.maskedinput.min.js
361 ms
style.css
360 ms
sow-social-media-buttons-atom-3a1fae9b4b7f.css
377 ms
foundation.js
345 ms
calculator.js
375 ms
core.min.js
363 ms
widget.min.js
359 ms
mouse.min.js
335 ms
slider.min.js
311 ms
jquery.selecttoui.min.js
317 ms
jquery.fitvids.js
318 ms
custom.js
351 ms
toolkit.js
269 ms
jquery.form.min.js
255 ms
scripts.js
287 ms
smush-lazy-load.min.js
284 ms
wp-embed.min.js
288 ms
jquery.cycle.swipe.min.js
284 ms
style.css
266 ms
css
156 ms
css
190 ms
gen_204
485 ms
darkwood.png
297 ms
banner_f24.jpg
310 ms
Sem-t%C3%ADtulo-300x226.jpg
291 ms
srhanse-300x300.png
294 ms
vender-300x194.jpeg
335 ms
WhatsApp-Image-2022-09-20-at-4.59.18-PM-270x220.jpeg
291 ms
WhatsApp-Image-2022-09-16-at-8.53.50-AM-270x220.jpeg
287 ms
WhatsApp-Image-2022-09-03-at-9.41.29-AM-Copia-270x220.jpeg
284 ms
reservado.png
280 ms
Fachada-1-270x220.jpeg
285 ms
SALA-PERIMETRAL-05-270x220.jpeg
294 ms
WhatsApp-Image-2022-07-21-at-12.24.23-270x220.jpeg
297 ms
WhatsApp-Image-2022-06-15-at-10.01.36-270x220.jpeg
296 ms
Fachada-270x220.jpeg
299 ms
01-Fachada-270x220.jpeg
297 ms
66c5e0fd-bd69-4674-87db-2030e553b40a-270x220.jpg
297 ms
41140545-8184-4511-ae66-a5da93c3c7bd-270x220.jpg
319 ms
CASA-01-270x220.jpeg
317 ms
TERRENO-01-1-270x220.jpeg
318 ms
TERRENO-270x220.jpeg
315 ms
WhatsApp-Image-2022-08-24-at-14.35.56-270x220.jpeg
319 ms
184fadec-ddf6-4df0-8524-646e03118663-270x220.jpg
343 ms
gilberto-diana-fernando-gumer-1-285x285.jpg
335 ms
WhatsApp-Image-2019-10-07-at-17.42.51-285x285.jpeg
343 ms
WhatsApp-Image-2017-05-15-at-09.14.05-C%C3%B3pia-1-285x285.jpeg
340 ms
Sem-t%C3%ADtulo-285x285.jpg
342 ms
contato_final_rodape-300x160.png
344 ms
u-4k0rCzjgs5J7oXnJcM_0kACGMtT-DfrdPrNX0.woff
665 ms
u-4k0rCzjgs5J7oXnJcM_0kACGMtT-7frdPrNX2-Ag.woff
906 ms
u-4k0rCzjgs5J7oXnJcM_0kACGMtT-PfrdPrNX2-Ag.woff
787 ms
u-4k0rCzjgs5J7oXnJcM_0kACGMtT-zfrdPrNX2-Ag.woff
783 ms
u-4k0rCzjgs5J7oXnJcM_0kACGMtT-TfrdPrNX2-Ag.woff
896 ms
u-4k0rCzjgs5J7oXnJcM_0kACGMtT-3frdPrNX2-Ag.woff
789 ms
0nkoC9_pNeMfhX4BhcH4bC7oqP4.woff
696 ms
0nkoC9_pNeMfhX4Bhc_4bC7oqP7NiA.woff
697 ms
shandora-icon.woff
661 ms
fontawesome-webfont.woff
313 ms
feature-background.woff
598 ms
fa-regular-400.woff
383 ms
fa-solid-900.woff
386 ms
fa-brands-400.woff
385 ms
print.css
108 ms
mask.png
17 ms
whanse.com 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.
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
Links do not have a discernible name
whanse.com 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
Issues were logged in the Issues panel in Chrome Devtools
whanse.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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whanse.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 Whanse.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.
whanse.com
Open Graph data is detected on the main page of W Hanse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: