3.7 sec in total
971 ms
2.5 sec
223 ms
Welcome to graiche.com.br homepage info - get ready to check Graiche best content for Brazil right away, or after learning these important things about graiche.com.br
Visit graiche.com.brWe analyzed Graiche.com.br page load time and found that the first response time was 971 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
graiche.com.br performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value25.3 s
0/100
25%
Value12.2 s
3/100
10%
Value340 ms
75/100
30%
Value0.15
76/100
15%
Value13.7 s
11/100
10%
971 ms
438 ms
296 ms
315 ms
296 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 58% of them (31 requests) were addressed to the original Graiche.com.br, 19% (10 requests) were made to Static.xx.fbcdn.net and 13% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Graiche.com.br.
Page size can be reduced by 338.9 kB (16%)
2.2 MB
1.8 MB
In fact, the total size of Graiche.com.br main page is 2.2 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 23.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 23.6 kB or 75% of the original size.
Potential reduce by 18.7 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. Graiche images are well optimized though.
Potential reduce by 268.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 268.3 kB or 84% of the original size.
Potential reduce by 28.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. Graiche.com.br needs all CSS files to be minified and compressed as it can save up to 28.3 kB or 84% of the original size.
Number of requests can be reduced by 13 (25%)
52
39
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Graiche. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
graiche.com.br
971 ms
global.css
438 ms
superfish.css
296 ms
hoverIntent.js
315 ms
superfish.js
296 ms
jquery.js
1174 ms
cycle.js
726 ms
icon_face.jpg
884 ms
icon_twitter.jpg
883 ms
icon_in.jpg
885 ms
icon_brasil.jpg
885 ms
logo.jpg
1029 ms
botao-via-express.jpg
887 ms
botao-fale-conosco.jpg
1024 ms
icon_mural.jpg
1029 ms
banner04.jpg
876 ms
banner.jpg
724 ms
banner01.jpg
1029 ms
banner03.jpg
883 ms
banner02.jpg
868 ms
img_gg.jpg
872 ms
icon_tc_laranja.jpg
876 ms
thumb.php
1225 ms
img-proposta.jpg
1019 ms
animation_gif.gif
1027 ms
banner_fco.jpg
1170 ms
banner_imoveis_destaque.jpg
1030 ms
all.js
72 ms
74 ms
xd_arbiter.php
90 ms
xd_arbiter.php
145 ms
seta_hover.jpg
377 ms
seta.jpg
377 ms
botao_busca.jpg
376 ms
botao_ok.jpg
377 ms
likebox.php
82 ms
C-D3sjGKj3j.css
88 ms
zEMlMNmIXUJ.css
109 ms
_rx8naC75Dy.js
145 ms
b94UUzHjapV.js
173 ms
0wM5s1Khldu.js
144 ms
TTCre3391I0.js
141 ms
581161_390938297618637_2031644240_n.jpg
95 ms
546415_390936137618853_765248006_n.jpg
70 ms
1798731_10152379251025913_7217100254341682270_n.jpg
73 ms
10624570_1391336247793575_173926494880582592_n.jpg
87 ms
574939_228374480639614_650722567_n.jpg
88 ms
12366303_1062361033785148_3125153256335428095_n.jpg
87 ms
10354686_10150004552801856_220367501106153455_n.jpg
85 ms
wL6VQj7Ab77.png
20 ms
s7jcwEQH7Sx.png
20 ms
I6-MnjEovm5.js
25 ms
f6T91Deal_q.js
25 ms
graiche.com.br 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 match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
graiche.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
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
graiche.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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Graiche.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Graiche.com.br main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
graiche.com.br
Open Graph description is not detected on the main page of Graiche. 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: