5.9 sec in total
540 ms
4.6 sec
718 ms
Click here to check amazing Synthesize content. Otherwise, check out these important facts you probably never knew about synthesize.com.br
A Synthesize é uma empresa no ramo de suplementos alimentares que tem como missão principal contribuir com os resultados de seus clientes.
Visit synthesize.com.brWe analyzed Synthesize.com.br page load time and found that the first response time was 540 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
synthesize.com.br performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value10.6 s
0/100
25%
Value9.2 s
13/100
10%
Value1,990 ms
8/100
30%
Value0.133
81/100
15%
Value11.9 s
17/100
10%
540 ms
354 ms
345 ms
153 ms
347 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 26% of them (18 requests) were addressed to the original Synthesize.com.br, 49% (33 requests) were made to Scontent.cdninstagram.com and 10% (7 requests) were made to Snapwidget.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Snapwidget.com.
Page size can be reduced by 281.1 kB (16%)
1.8 MB
1.5 MB
In fact, the total size of Synthesize.com.br main page is 1.8 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.5 MB which makes up the majority of the site volume.
Potential reduce by 7.7 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 7.7 kB or 79% of the original size.
Potential reduce by 91.8 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. Synthesize images are well optimized though.
Potential reduce by 127.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 127.6 kB or 64% of the original size.
Potential reduce by 53.9 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. Synthesize.com.br needs all CSS files to be minified and compressed as it can save up to 53.9 kB or 81% of the original size.
Number of requests can be reduced by 20 (30%)
66
46
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Synthesize. 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.
synthesize.com.br
540 ms
utopian.css
354 ms
nivo-slider.css
345 ms
jquery.min.js
153 ms
jquery.nivo.slider.pack.js
347 ms
2510 ms
BgPages.jpg
1033 ms
SynthesizeLogo.png
359 ms
3w_whey.jpg
1239 ms
SynthesizeBarraBg.png
357 ms
BgFooter.jpg
2167 ms
pixelTrans.png
351 ms
transB.png
510 ms
facebook_32.png
514 ms
insta.png
684 ms
twitter.png
852 ms
pin.png
695 ms
youtube.png
861 ms
mail.png
880 ms
images.jpg
1826 ms
combined.css
20 ms
smoothDivScroll.css
44 ms
stack_161235.js
191 ms
jquery.min.js
131 ms
jquery-ui.min.js
98 ms
jquery.mousewheel.min.js
30 ms
jquery.kinetic.js
56 ms
jquery.smoothdivscroll-1.3-min.js
45 ms
analytics.js
134 ms
stackpile.api-db10b4428c.js
134 ms
1170995_742465645889566_84111492_n.jpg
332 ms
12145108_1680622388893908_1707238950_n.jpg
319 ms
12783964_1507317509576790_1175278790_n.jpg
264 ms
12750136_971168382962903_435659835_n.jpg
313 ms
12725107_1132600173439378_1376892436_n.jpg
285 ms
12783935_1696761737231895_364613165_n.jpg
300 ms
12677319_228480200822991_656263822_n.jpg
363 ms
12750126_1527933160844100_1656449583_n.jpg
378 ms
12724852_1769548159944558_1704542939_n.jpg
378 ms
12677266_997973456934352_1131624540_n.jpg
395 ms
12724844_153886834994962_1671964905_n.jpg
391 ms
12748297_1727116724189255_1584273538_n.jpg
420 ms
12751218_1032753960108724_1974711121_n.jpg
471 ms
12599234_1683055615298307_1055210509_n.jpg
474 ms
12716814_1688434544765520_821025012_n.jpg
471 ms
12627898_1050394761649226_1929241805_n.jpg
510 ms
12628123_1560377624278549_1659119866_n.jpg
510 ms
12534294_1727823850782057_807054053_n.jpg
524 ms
12547123_955470884544037_2017716562_n.jpg
553 ms
12556067_213412022342671_2043074284_n.jpg
603 ms
12558863_185723548452934_1358046115_n.jpg
583 ms
12558741_1543261472653320_778144519_n.jpg
620 ms
12556107_1675086942733627_918347547_n.jpg
615 ms
12547385_1564165547240044_1079324365_n.jpg
624 ms
12543335_1679445488939654_1277845638_n.jpg
705 ms
12556049_810432169085342_2128204428_n.jpg
709 ms
12627866_684039628365956_256230284_n.jpg
724 ms
12479190_1496246750685232_58241633_n.jpg
724 ms
11254147_566316303515935_1329811949_n.jpg
726 ms
12599125_539006799594317_2013627637_n.jpg
734 ms
12599095_871629902968383_672243706_n.jpg
828 ms
12501763_428109910732764_1436842602_n.jpg
832 ms
12627905_770115163118483_634413959_n.jpg
829 ms
stackpile.api-db10b4428c.js
72 ms
big_transparent.gif
46 ms
collect
27 ms
collect
101 ms
nr-892.min.js
90 ms
synthesize.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-hidden="true"] elements contain focusable descendents
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.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
Links do not have a discernible name
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 [lang] attribute
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>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
synthesize.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
synthesize.com.br 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Synthesize.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 Synthesize.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.
synthesize.com.br
Open Graph description is not detected on the main page of Synthesize. 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: