3.5 sec in total
724 ms
2.5 sec
249 ms
Click here to check amazing Terminologia content. Otherwise, check out these important facts you probably never knew about terminologia.com.br
Dicionário de palavras relacionadas à saúde
Visit terminologia.com.brWe analyzed Terminologia.com.br page load time and found that the first response time was 724 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
terminologia.com.br performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value7.8 s
3/100
25%
Value11.5 s
5/100
10%
Value7,250 ms
0/100
30%
Value0.27
45/100
15%
Value17.9 s
4/100
10%
724 ms
118 ms
355 ms
241 ms
270 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 44% of them (25 requests) were addressed to the original Terminologia.com.br, 39% (22 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (724 ms) belongs to the original domain Terminologia.com.br.
Page size can be reduced by 282.7 kB (61%)
459.8 kB
177.1 kB
In fact, the total size of Terminologia.com.br main page is 459.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 219.1 kB which makes up the majority of the site volume.
Potential reduce by 21.4 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 21.4 kB or 74% of the original size.
Potential reduce by 14.4 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. Obviously, Terminologia needs image optimization as it can save up to 14.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 141.5 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 141.5 kB or 65% of the original size.
Potential reduce by 105.4 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. Terminologia.com.br needs all CSS files to be minified and compressed as it can save up to 105.4 kB or 80% of the original size.
Number of requests can be reduced by 26 (79%)
33
7
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Terminologia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.terminologia.com.br
724 ms
wp-emoji-release.min.js
118 ms
polls-css.css
355 ms
style.css
241 ms
style-mobile.css
270 ms
font-awesome.css
272 ms
css
24 ms
jetpack.css
244 ms
jquery.js
337 ms
jquery-migrate.min.js
369 ms
jquery.fitvids.js
368 ms
hoverIntent.js
382 ms
superfish.js
382 ms
loader.js
129 ms
wotd2.js
11 ms
ck-karma.js
458 ms
jquery.cycle.js
528 ms
slideshow-shortcode.js
494 ms
photon.js
492 ms
polls-js.js
496 ms
devicepx-jetpack.js
4 ms
gprofiles.js
55 ms
wpgroho.js
497 ms
jquery.custom.js
561 ms
navigation.js
588 ms
wp-embed.min.js
556 ms
e-201611.js
4 ms
wotd2.js
18 ms
fundo-terminologia_final.png
116 ms
logo-terminologia_final.png
290 ms
banner_300x60.gif
290 ms
Pru33qjShpZSmG3z6VYwnT8E0i7KZn-EPnyo3HZu7kw.woff
19 ms
idLYXfFa1c7oAPILDl4z0fesZW2xOQ-xsNqO47m55DA.woff
19 ms
Xyjz-jNkfiYuJf8UC3Lizw.woff
20 ms
oOeFwZNlrTefzLYmlVV1UD8E0i7KZn-EPnyo3HZu7kw.woff
21 ms
97uahxiqZRoncBaCEI3aWz8E0i7KZn-EPnyo3HZu7kw.woff
20 ms
9_7S_tWeGDh5Pq3u05RVkj8E0i7KZn-EPnyo3HZu7kw.woff
20 ms
QQt14e8dY39u-eYBZmppwTqR_3kx9_hJXbbyU8S6IN0.woff
19 ms
STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff
21 ms
WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff
20 ms
QoPu455RxV2raYSIFXAMBRsxEYwM7FgeyaSgU71cLG0.woff
20 ms
Ji5epXNcpHu3r63lhS0cThsxEYwM7FgeyaSgU71cLG0.woff
21 ms
Li18TEFObx_yGdzKDoI_chsxEYwM7FgeyaSgU71cLG0.woff
21 ms
vQbQAx9WlNOTTgpOnfyPXQ.woff
21 ms
ZKwULyCG95tk6mOqHQfRBBsxEYwM7FgeyaSgU71cLG0.woff
21 ms
cbAbzEjxTdN5KKmS-gA0tRsxEYwM7FgeyaSgU71cLG0.woff
21 ms
rr0ijB5_2nAJsAoZ6vECXT8E0i7KZn-EPnyo3HZu7kw.woff
25 ms
fontawesome-webfont.woff
393 ms
7m8l7TlFO-S3VkhHuR0at9Ih4imgI8P11RFo6YPCPC0.woff
24 ms
dzxs_VxZUhdM2mEBkNa8shsxEYwM7FgeyaSgU71cLG0.woff
25 ms
dFWsweFqlD8ExfyN7Gh_GPesZW2xOQ-xsNqO47m55DA.woff
25 ms
OLffGBTaF0XFOW1gnuHF0dIh4imgI8P11RFo6YPCPC0.woff
25 ms
t6Nd4cfPRhZP44Q5QAjcC9Ih4imgI8P11RFo6YPCPC0.woff
26 ms
bmC0pGMXrhphrZJmniIZpdIh4imgI8P11RFo6YPCPC0.woff
26 ms
hovercard.css
27 ms
services.css
54 ms
g.gif
3 ms
terminologia.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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
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.
terminologia.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
Browser errors were logged to the console
terminologia.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
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
![]()
EN
![]()
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Terminologia.com.br can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Terminologia.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.
terminologia.com.br
Open Graph data is detected on the main page of Terminologia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: