4 sec in total
160 ms
3.3 sec
619 ms
Visit foxter.com.br now to see the best up-to-date Foxter content and also check out these interesting facts you probably never knew about foxter.com.br
Foxter Cia Imobiliária - Encontre as melhores ofertas imobiliárias em Porto Alegre. Casas e Apartamentos Residenciais e Comerciais
Visit foxter.com.brWe analyzed Foxter.com.br page load time and found that the first response time was 160 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
foxter.com.br performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value7.1 s
5/100
25%
Value7.7 s
24/100
10%
Value2,410 ms
5/100
30%
Value0.248
50/100
15%
Value17.4 s
4/100
10%
160 ms
884 ms
239 ms
236 ms
234 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Foxter.com.br, 18% (20 requests) were made to Static.xx.fbcdn.net and 11% (12 requests) were made to Cdn-my.konecty.com. The less responsive or slowest element that took the longest time to load (884 ms) relates to the external source Foxterciaimobiliaria.com.br.
Page size can be reduced by 245.4 kB (21%)
1.1 MB
897.9 kB
In fact, the total size of Foxter.com.br 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. 75% 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 853.5 kB which makes up the majority of the site volume.
Potential reduce by 178.8 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. This page needs HTML code to be minified as it can gain 30.9 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 178.8 kB or 86% of the original size.
Potential reduce by 13.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. Foxter images are well optimized though.
Potential reduce by 53.2 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 53.2 kB or 64% of the original size.
Number of requests can be reduced by 54 (56%)
96
42
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foxter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
foxter.com.br
160 ms
www.foxterciaimobiliaria.com.br
884 ms
serve
239 ms
serve
236 ms
serve
234 ms
masthead-02.jpg
309 ms
app-foxter1.png
26 ms
logo_200x50.png
6 ms
supreme-mast.jpg
359 ms
app-store.png
26 ms
play-store.png
25 ms
form-alerta.png
76 ms
analytics.js
23 ms
gtm.js
73 ms
fontello.woff
50 ms
museo-500-regular.otf
50 ms
collect
27 ms
form-enviar.png
21 ms
collect
187 ms
collect
6 ms
conversion_async.js
134 ms
fbds.js
141 ms
collect
140 ms
konchat.js
162 ms
infscroll.gif
49 ms
apto_res.jpg
104 ms
comercial_01.jpg
156 ms
casa_01.jpg
121 ms
pr%C3%A9-lan_01.jpg
155 ms
casa_02.jpg
150 ms
casa_03.jpg
122 ms
comercial_02.jpg
170 ms
cobertura_01.jpg
186 ms
bairro-planejado.jpg
192 ms
tour-virtual-capa.jpg
219 ms
ga-audiences
60 ms
59 ms
63 ms
72 ms
ga-audiences
46 ms
collect
11 ms
33 ms
37 ms
konchat.css
57 ms
19 ms
16 ms
29 ms
sdk.js
52 ms
platform.js
51 ms
visitor.foxter.konecty.com
18 ms
5 ms
44edd8abe6601fe560385c799a125d0a45e530d9.css
28 ms
55f0c3c8fa93e597d1c22bb39e0d7eb20363541b.js
133 ms
css
68 ms
cb=gapi.loaded_0
205 ms
cb=gapi.loaded_1
205 ms
page
318 ms
275 ms
xd_arbiter.php
247 ms
xd_arbiter.php
462 ms
gtm.js
146 ms
pt.json
326 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
90 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
90 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
97 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
96 ms
postmessageRelay
217 ms
info
55 ms
rs=AGLTcCN5hwoG1Q-pa8DbuzSJkPzxm55V9w
35 ms
rs=AGLTcCOUAbJHq2UB-s9qxmjkpcMyt2yJiQ
51 ms
rs=AGLTcCOEMSWk6UjLYYp7ZqY1CUjDhFT-Fg
93 ms
photo.jpg
212 ms
rs=AGLTcCOEMSWk6UjLYYp7ZqY1CUjDhFT-Fg
45 ms
3193398744-postmessagerelay.js
145 ms
rpc:shindig_random.js
78 ms
collect
35 ms
collect
54 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
121 ms
JcQUq3K39RZrUxrrs7pjpwLUuEpTyoUstqEm5AMlJo4.ttf
135 ms
IhuqmeHx65TaW6CiR2l0VALUuEpTyoUstqEm5AMlJo4.ttf
141 ms
like_box.php
151 ms
rs=AGLTcCOEMSWk6UjLYYp7ZqY1CUjDhFT-Fg
42 ms
cb=gapi.loaded_0
9 ms
ebiMDO3r-8l.css
82 ms
jGc-59L_9lo.css
102 ms
k5BhlqovqZn.css
120 ms
q68gy-v_YMF.js
169 ms
FJmpeSpHpjS.js
192 ms
0wM5s1Khldu.js
138 ms
1bNoFZUdlYZ.js
135 ms
OloiM1PZafe.js
137 ms
LTv6ZK-5zxz.js
213 ms
1FCa-btixu2.js
211 ms
Oagsvfb4VWi.js
212 ms
pObvZSrFc_4.js
211 ms
HgJbVwzBr8E.js
212 ms
H3EKDTObx05.js
261 ms
OZFAYTv-ZUg.js
265 ms
12565595_1111172482239803_1079094121720915295_n.png
206 ms
542714_506511819372542_1362968422_n.jpg
221 ms
12510324_948113271932730_434483268845405368_n.jpg
240 ms
12191398_10207974042412444_4277481000666569160_n.jpg
257 ms
12316274_531821943644282_5660339613457967690_n.jpg
259 ms
12814799_1020762594683467_7235449471338241812_n.jpg
259 ms
12239530_121507964880727_8477493911461849270_n.jpg
260 ms
1920332_844854108932922_2107247004907140593_n.jpg
260 ms
12806252_1140227832657156_7766095369087854286_n.jpg
389 ms
12239658_768228569950258_7115358057224405780_n.jpg
274 ms
wL6VQj7Ab77.png
130 ms
s7jcwEQH7Sx.png
129 ms
gxbPuQdXIZP.png
20 ms
I6-MnjEovm5.js
23 ms
pQrUxxo5oQp.js
24 ms
foxter.com.br accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
foxter.com.br 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
Page has valid source maps
foxter.com.br 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
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foxter.com.br 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 Foxter.com.br 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.
foxter.com.br
Open Graph description is not detected on the main page of Foxter. 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: