4.1 sec in total
600 ms
3 sec
499 ms
Visit thinkingheads.com now to see the best up-to-date Thinking Heads content for Uzbekistan and also check out these interesting facts you probably never knew about thinkingheads.com
Agencia de conferenciantes y posicionamiento de líderes. En Thinking Heads trabajamos con referentes internacionales. ¡Elige al mejor!
Visit thinkingheads.comWe analyzed Thinkingheads.com page load time and found that the first response time was 600 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
thinkingheads.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value18.4 s
0/100
25%
Value15.4 s
0/100
10%
Value6,230 ms
0/100
30%
Value0.328
35/100
15%
Value26.1 s
0/100
10%
600 ms
39 ms
41 ms
66 ms
452 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 72% of them (109 requests) were addressed to the original Thinkingheads.com, 13% (19 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (949 ms) belongs to the original domain Thinkingheads.com.
Page size can be reduced by 286.3 kB (16%)
1.8 MB
1.6 MB
In fact, the total size of Thinkingheads.com 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. Only a small number of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 267.2 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 267.2 kB or 82% of the original size.
Potential reduce by 2.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. Thinking Heads images are well optimized though.
Potential reduce by 8.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 7.8 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. Thinkingheads.com has all CSS files already compressed.
Number of requests can be reduced by 119 (90%)
132
13
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thinking Heads. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 94 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
thinkingheads.com
600 ms
css
39 ms
css
41 ms
2829127.js
66 ms
mediaelementplayer-legacy.min.css
452 ms
wp-mediaelement.min.css
449 ms
views-frontend.css
454 ms
editor-style-shared.css
451 ms
styles.css
455 ms
wpcf7-redirect-frontend.min.css
456 ms
styles.css
461 ms
style.min.css
460 ms
style.min.css
457 ms
cms-navigation-base.css
457 ms
cms-navigation.css
464 ms
style.css
501 ms
bootstrap.css
550 ms
toolset-common.css
485 ms
all.css
52 ms
elementor-icons.min.css
475 ms
frontend-lite.min.css
477 ms
swiper.min.css
493 ms
frontend-lite.min.css
558 ms
js_composer.min.css
750 ms
custom.css
556 ms
v4-shims.css
73 ms
css
43 ms
toolset-common-es-frontend.js
589 ms
jquery.min.js
689 ms
jquery-migrate.min.js
628 ms
script.min.js
629 ms
gtm.js
73 ms
fb.js
126 ms
2829127.js
130 ms
collectedforms.js
177 ms
2829127.js
178 ms
widget-icon-box.min.css
553 ms
animations.min.css
614 ms
wp-polyfill-inert.min.js
621 ms
regenerator-runtime.min.js
622 ms
wp-polyfill.min.js
634 ms
hooks.min.js
854 ms
i18n.min.js
859 ms
url.min.js
854 ms
api-fetch.min.js
855 ms
react.min.js
858 ms
api.js
142 ms
v2.js
139 ms
react-dom.min.js
856 ms
js
71 ms
destination
70 ms
analytics.js
29 ms
dom-ready.min.js
756 ms
collect
210 ms
collect
54 ms
a11y.min.js
509 ms
blob.min.js
508 ms
autop.min.js
509 ms
block-serialization-default-parser.min.js
507 ms
deprecated.min.js
506 ms
dom.min.js
543 ms
escape-html.min.js
540 ms
element.min.js
543 ms
is-shallow-equal.min.js
538 ms
keycodes.min.js
562 ms
priority-queue.min.js
554 ms
compose.min.js
641 ms
private-apis.min.js
637 ms
redux-routine.min.js
640 ms
data.min.js
628 ms
ga-audiences
89 ms
html-entities.min.js
619 ms
rich-text.min.js
565 ms
shortcode.min.js
696 ms
blocks.min.js
791 ms
moment.min.js
668 ms
date.min.js
719 ms
primitives.min.js
627 ms
warning.min.js
614 ms
components.min.js
949 ms
keyboard-shortcuts.min.js
660 ms
commands.min.js
653 ms
notices.min.js
739 ms
preferences-persistence.min.js
732 ms
preferences.min.js
512 ms
style-engine.min.js
512 ms
token-list.min.js
511 ms
wordcount.min.js
513 ms
block-editor.min.js
856 ms
htcontactform-block.js
529 ms
index.js
550 ms
index.js
550 ms
wpcf7r-fe.js
594 ms
custom.js
610 ms
bootstrap.min.js
631 ms
ddl-tabs-cell-frontend.js
629 ms
fbevents.js
161 ms
js
64 ms
insight.min.js
164 ms
zYX9KVElMYYaJe8bpLHnCwDKjR7_AIFscQ.ttf
165 ms
zYXgKVElMYYaJe8bpLHnCwDKhdHeEA.ttf
238 ms
zYX9KVElMYYaJe8bpLHnCwDKjSL9AIFscQ.ttf
300 ms
zYX9KVElMYYaJe8bpLHnCwDKjWr7AIFscQ.ttf
300 ms
NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf
299 ms
NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzZg.ttf
300 ms
NaPDcZTIAOhVxoMyOr9n_E7ffAzHGItzZg.ttf
301 ms
NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzZg.ttf
301 ms
NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZg.ttf
343 ms
NaPDcZTIAOhVxoMyOr9n_E7ffEDBGItzZg.ttf
344 ms
j8_96_fAw7jrcalD7oKYNX0QfAnPcbzNEEB7OoicBw7FYWqXNRA.ttf
344 ms
j8_96_fAw7jrcalD7oKYNX0QfAnPcbzNEEB7OoicBw73YWqXNRA.ttf
382 ms
j8_96_fAw7jrcalD7oKYNX0QfAnPcbzNEEB7OoicBw4iZmqXNRA.ttf
343 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
341 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
380 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
380 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
397 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
381 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
395 ms
wp-gallery-custom-links.js
680 ms
index.js
654 ms
smush-lazy-load.min.js
673 ms
js_composer_front.min.js
681 ms
webpack-pro.runtime.min.js
735 ms
webpack.runtime.min.js
719 ms
frontend-modules.min.js
707 ms
frontend.min.js
633 ms
waypoints.min.js
642 ms
core.min.js
725 ms
frontend.min.js
725 ms
elements-handlers.min.js
727 ms
underscore.min.js
724 ms
insight_tag_errors.gif
267 ms
wp-util.min.js
599 ms
frontend.min.js
674 ms
datepicker.min.js
676 ms
mouse.min.js
678 ms
slider.min.js
591 ms
jquery.ui.touch-punch.js
580 ms
mediaelement-and-player.min.js
583 ms
mediaelement-migrate.min.js
593 ms
wp-mediaelement.min.js
529 ms
backbone.min.js
543 ms
wp-playlist.min.js
569 ms
views-frontend.js
556 ms
header-home-20-aniv_back.jpg
792 ms
madrid.jpg
684 ms
miami.jpg
668 ms
seul.jpg
641 ms
recaptcha__en.js
41 ms
SearchIconWhite.svg
319 ms
Telephone.svg
321 ms
re-thinking-3.png
357 ms
thinkingheads.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
thinkingheads.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
thinkingheads.com 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
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thinkingheads.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Thinkingheads.com 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.
thinkingheads.com
Open Graph data is detected on the main page of Thinking Heads. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: