8.6 sec in total
1.2 sec
7 sec
376 ms
Click here to check amazing Vivabemcomparkinson content for Brazil. Otherwise, check out these important facts you probably never knew about vivabemcomparkinson.com.br
Acesse o site da Roche Brasil.
Visit vivabemcomparkinson.com.brWe analyzed Vivabemcomparkinson.com.br page load time and found that the first response time was 1.2 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
vivabemcomparkinson.com.br performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value11.2 s
0/100
25%
Value6.8 s
34/100
10%
Value860 ms
33/100
30%
Value0.51
15/100
15%
Value11.9 s
17/100
10%
1239 ms
710 ms
1566 ms
58 ms
27 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 23% of them (28 requests) were addressed to the original Vivabemcomparkinson.com.br, 30% (37 requests) were made to Maps.googleapis.com and 12% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Vivabemcomparkinson.com.br.
Page size can be reduced by 1.1 MB (57%)
2.0 MB
864.3 kB
In fact, the total size of Vivabemcomparkinson.com.br main page is 2.0 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. 60% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 22.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 22.6 kB or 74% of the original size.
Potential reduce by 12.2 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. Vivabemcomparkinson images are well optimized though.
Potential reduce by 867.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 867.6 kB or 68% of the original size.
Potential reduce by 243.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. Vivabemcomparkinson.com.br needs all CSS files to be minified and compressed as it can save up to 243.1 kB or 84% of the original size.
Number of requests can be reduced by 59 (51%)
116
57
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vivabemcomparkinson. 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 5 to 1 for CSS and as a result speed up the page load time.
vivabemcomparkinson.com.br
1239 ms
main.css
710 ms
roche-parkinson.js
1566 ms
js
58 ms
infobox.js
27 ms
jquery.slimscroll.min.js
421 ms
maps.js
549 ms
mapa.css
422 ms
analytics.js
53 ms
sdk.js
278 ms
logo.png
311 ms
bg-white.png
144 ms
player_api
49 ms
bg-highlight.jpg
431 ms
bg-flower.jpg
500 ms
ico-flower.png
275 ms
dots-145x1.png
538 ms
btn-facebook-connect.jpg
259 ms
pattern-gray-diagonal-stripes.jpg
398 ms
btn-services-cuidadores.jpg
535 ms
btn-services-medicamentos.jpg
549 ms
lupa-01.png
541 ms
bn-youtube.jpg
1020 ms
brand-abp.png
648 ms
brand-roche.jpg
675 ms
btn-carousel-prev.png
676 ms
btn-carousel-next.png
683 ms
MuseoSans_700-webfont.woff
816 ms
MuseoSans-100-webfont.woff
938 ms
MuseoSans-700Italic-webfont.woff
949 ms
MuseoSans_500_Italic-webfont.woff
1687 ms
MuseoSans-300-webfont.woff
965 ms
collect
13 ms
www-widgetapi.js
4 ms
VLCLqJ-KLc8
75 ms
www-embed-player-vflfNyN_r.css
29 ms
www-embed-player.js
55 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
75 ms
ad_status.js
57 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
59 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
61 ms
127 ms
xd_arbiter.php
226 ms
xd_arbiter.php
433 ms
common.js
22 ms
util.js
35 ms
geocoder.js
21 ms
map.js
26 ms
geometry.js
27 ms
directions.js
64 ms
controls.js
63 ms
places_impl.js
23 ms
onion.js
25 ms
openhand_8_8.cur
78 ms
ViewportInfoService.GetViewportInfo
125 ms
stats.js
63 ms
infowindow.js
50 ms
css
46 ms
marker.js
43 ms
transparent.png
62 ms
powered-by-google-on-white3.png
63 ms
autocomplete-icons.png
65 ms
page.php
432 ms
google4.png
29 ms
mapcnt6.png
26 ms
sv5.png
27 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
22 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
27 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
26 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
25 ms
tmapctrl.png
27 ms
cb_scout5.png
77 ms
tmapctrl4.png
27 ms
imgs8.png
76 ms
vt
51 ms
vt
59 ms
vt
48 ms
vt
49 ms
vt
42 ms
vt
40 ms
vt
78 ms
vt
78 ms
vt
83 ms
vt
80 ms
vt
92 ms
vt
85 ms
vt
116 ms
vt
122 ms
vt
113 ms
vt
111 ms
vt
139 ms
vt
120 ms
vt
161 ms
vt
170 ms
vt
143 ms
vt
148 ms
AuthenticationService.Authenticate
277 ms
4n08FrZmW0I.css
281 ms
q68gy-v_YMF.js
416 ms
XoqZARH4OJa.js
618 ms
ihptErjAmMX.js
553 ms
897 ms
10409136_861043950602383_5174879162831776995_n.png
676 ms
1779824_861043300602448_2057623354628881714_n.png
816 ms
12791068_1062365897152992_9094361226596395038_n.jpg
877 ms
12718310_637898199684494_6719834617344387794_n.jpg
906 ms
12744502_10204193820165389_2261067177681849357_n.jpg
876 ms
12115958_524062427759154_151501321305271168_n.jpg
942 ms
12805686_1038243992914868_1231561018198376783_n.jpg
961 ms
12662675_804241196348703_398182999468012810_n.jpg
956 ms
1915609_972686869491744_1053955062542543088_n.jpg
944 ms
10562931_700353626724430_3622933724637728776_n.jpg
1014 ms
11914904_1128723447142147_401369153469003991_n.jpg
1067 ms
12646967_169530416748983_314957276290221326_n.jpg
1037 ms
12805982_973305319371358_5558741659363665785_n.jpg
1205 ms
12321674_992819720754433_7401127417850222939_n.jpg
1083 ms
12670049_891066907676424_8803490950755207813_n.jpg
1067 ms
wL6VQj7Ab77.png
70 ms
s7jcwEQH7Sx.png
69 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
71 ms
0JBr1QHp8Gi.js
69 ms
kDOzhTr2W91.js
136 ms
vivabemcomparkinson.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
[aria-*] attributes do not have valid values
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
Some elements have a [tabindex] value greater than 0
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.
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.
vivabemcomparkinson.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
Missing source maps for large first-party JavaScript
vivabemcomparkinson.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vivabemcomparkinson.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 Vivabemcomparkinson.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.
vivabemcomparkinson.com.br
Open Graph data is detected on the main page of Vivabemcomparkinson. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: