4.3 sec in total
57 ms
3.8 sec
413 ms
Welcome to think-king.com homepage info - get ready to check Think King best content right away, or after learning these important things about think-king.com
Think King stroller and wheelchair travel accessories. The original Mighty Buggy Hook, Jumbo Swirly Hook, Clippy Hook, SitAlong Toddler Luggage Seat, Soft Buggy Cup and Reusable Buggy Tote.
Visit think-king.comWe analyzed Think-king.com page load time and found that the first response time was 57 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
think-king.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value19.2 s
0/100
25%
Value9.0 s
14/100
10%
Value3,280 ms
2/100
30%
Value0.294
41/100
15%
Value22.0 s
1/100
10%
57 ms
1441 ms
47 ms
30 ms
90 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 79% of them (106 requests) were addressed to the original Think-king.com, 6% (8 requests) were made to Fonts.gstatic.com and 5% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Think-king.com.
Page size can be reduced by 191.8 kB (18%)
1.1 MB
867.1 kB
In fact, the total size of Think-king.com main page is 1.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 581.6 kB which makes up the majority of the site volume.
Potential reduce by 186.9 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 186.9 kB or 84% of the original size.
Potential reduce by 7 B
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. Think King images are well optimized though.
Potential reduce by 4.1 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 726 B
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. Think-king.com has all CSS files already compressed.
Number of requests can be reduced by 113 (92%)
123
10
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Think King. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 51 to 1 for CSS and as a result speed up the page load time.
think-king.com
57 ms
think-king.com
1441 ms
css
47 ms
style.min.css
30 ms
autoptimize_single_eade318fbed91c096467dffa56406638.php
90 ms
autoptimize_single_d3ec229e04c8634c88cc4cb3f2934c11.php
253 ms
autoptimize_single_e060b318326352285079b37601a9b8fe.php
259 ms
autoptimize_single_a84bbf125b1397539bd2956c190eaaa6.php
261 ms
autoptimize_single_3d5592ff164ae469333dfe3de106ac24.php
251 ms
autoptimize_single_d92dc367a7b427731d40e402aae21bac.php
317 ms
autoptimize_single_4c7759fae3d4ded686f116e14117f2ed.php
168 ms
autoptimize_single_3fd2afa98866679439097f4ab102fe0a.php
246 ms
autoptimize_single_e42af4e35c2149b331edd2691ad5ca49.php
326 ms
autoptimize_single_279a41fe094a1c0ff59f6d84dc6ec0d2.php
341 ms
autoptimize_single_fbb8a1986bb50beaed0e2e067a4092a7.php
345 ms
autoptimize_single_720f1385d1f57d0d3f4fa8a631835fb8.php
342 ms
styles.min.css
271 ms
flickity.min.css
286 ms
main.min.css
299 ms
autoptimize_single_8e2f6ed38d662dc1a91f4277877ae39c.php
375 ms
dashicons.min.css
338 ms
autoptimize_single_e6836d39a559417825a33c168d0cf4ad.php
408 ms
autoptimize_single_fc2eb56a084b87b1579ac4308eca79dc.php
415 ms
autoptimize_single_a50f35974aef83cd078f84ce17db2a3d.php
419 ms
autoptimize_single_5da870932f61abe6e179b16fbc094183.php
417 ms
autoptimize_single_4834907af10e4e69cece834089d791bc.php
425 ms
autoptimize_single_61d06ce7d5eae222bdd0f71d3f15d69d.php
454 ms
social-media.min.css
420 ms
social-sharing.min.css
433 ms
autoptimize_single_9ed6c04ed63c185986d33e9907a0e704.php
491 ms
photoswipe.min.css
431 ms
default-skin.min.css
432 ms
autoptimize_single_1e82f9b2faaa50da0ff21b3ca2f43e22.php
501 ms
js_composer.min.css
463 ms
autoptimize_single_1421875321a55903ef6dec39b3cdec47.php
513 ms
autoptimize_single_0a224d6dcce6761b15199a9c0ed1d8fc.php
564 ms
style.css
475 ms
autoptimize_single_155afb7d5ca08b441d97a0ae11e0e26b.php
550 ms
45862fdbc0.js
76 ms
js
104 ms
api.js
48 ms
iframe_api
47 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
65 ms
autoptimize_single_9c23e4e35fb83d64c7f8841816ef76ac.php
537 ms
autoptimize_single_bf9d2ad2b49f59a130829909784c447d.php
554 ms
autoptimize_single_d7a8127861fe37f332ec855349a23c3d.php
513 ms
animate.min.css
361 ms
vc_carousel.min.css
298 ms
jquery.min.js
317 ms
jquery-migrate.min.js
308 ms
jquery.blockUI.min.js
326 ms
add-to-cart.min.js
321 ms
js.cookie.min.js
317 ms
woocommerce.min.js
298 ms
autoptimize_single_787fe4f547a6cb7f4ce4934641085910.php
349 ms
photoswipe.min.js
270 ms
photoswipe-ui-default.min.js
265 ms
fingerprint.min.js
257 ms
lazysizes.min.js
260 ms
jquery.selectBox.min.js
264 ms
jquery.prettyPhoto.min.js
257 ms
jquery.yith-wcwl.min.js
236 ms
autoptimize_single_b8c17cb883cd0c89378236790e6f44bf.php
266 ms
autoptimize_single_24097abf1a9569f71ec6123fd2a6dc39.php
261 ms
wp-polyfill-inert.min.js
199 ms
regenerator-runtime.min.js
201 ms
wp-polyfill.min.js
209 ms
hooks.min.js
206 ms
i18n.min.js
203 ms
autoptimize_single_efc27e253fae1b7b891fb5a40e687768.php
277 ms
autoptimize_single_0b1719adf5fa7231cb1a1b54cf11a50e.php
276 ms
flickity.pkgd.min.js
194 ms
accounting.min.js
184 ms
main.min.js
184 ms
foundation.core.min.js
181 ms
foundation.util.mediaQuery.min.js
172 ms
foundation.util.keyboard.min.js
170 ms
foundation.offcanvas.min.js
158 ms
imagesloaded.pkgd.min.js
154 ms
styles.css
155 ms
css
30 ms
styles.css
147 ms
styles.css
143 ms
styles.css
144 ms
styles.css
133 ms
styles.css
145 ms
styles.css
151 ms
autoptimize_single_f4781564338c645e9b93a64d6a40f32e.php
319 ms
fresco.min.js
141 ms
autoptimize_single_10e85c7764bb0ed62f4d39fab4ae7b9d.php
323 ms
autoptimize_single_91f1d2e548b4a0a96b31aeea1865c4ce.php
322 ms
autoptimize_single_d85532113660ede3dbee81211377173c.php
320 ms
autoptimize_single_2588abc19e162ae4a8cd9eb5e9c65c56.php
315 ms
autoptimize_single_67b6b7b41bbe7b75352cef13f7777fe7.php
311 ms
main.min.js
310 ms
sourcebuster.min.js
367 ms
order-attribution.min.js
364 ms
autoptimize_single_9ee158518d037d5b6dbef092ef03c9c3.php
457 ms
autoptimize_single_ec0187677793456f98473f49d9e9b95f.php
368 ms
js_composer_front.min.js
349 ms
autoptimize_single_7b3c6d6b64594f45696a0e6bd0d96087.php
439 ms
longdesc.min.js
350 ms
wp-accessibility.min.js
348 ms
isotope.pkgd.min.js
335 ms
autoptimize_single_be02697d2cf7e6d3712c95d18de9eea2.php
425 ms
vc-waypoints.min.js
408 ms
transition.min.js
415 ms
vc_carousel.min.js
400 ms
S6uyw4BMUTPHjx4wWA.woff
79 ms
S6u9w4BMUTPHh7USSwiPHw.woff
78 ms
S6u9w4BMUTPHh6UVSwiPHw.woff
164 ms
S6u_w4BMUTPHjxsI5wq_Gwfr.woff
170 ms
S6u8w4BMUTPHjxsAXC-s.woff
256 ms
S6u_w4BMUTPHjxsI9w2_Gwfr.woff
257 ms
Shopkeeper-Icon-Font.ttf
441 ms
ThinkKing_logo_web.svg
196 ms
recaptcha__en.js
182 ms
ThinkKing-hooks-stroller.jpg
173 ms
www-widgetapi.js
172 ms
ThinkKing-clippy-hook-black-350x435.jpg
150 ms
mbE8H_G4Rmg
139 ms
autoptimize_single_29ed0396622780590223cd919f310dd7.php
88 ms
www-player.css
12 ms
www-embed-player.js
51 ms
base.js
92 ms
ad_status.js
140 ms
s9i9Iyk4Y_s1LD6aqz2X9kjqPppJUVpoTsMZDucYENo.js
56 ms
embed.js
40 ms
AIdro_m3ggeSonbrprwMJoahl6UorzbPRKmpP5BXMK4xorZmMQ=s68-c-k-c0x00ffffff-no-rj
456 ms
KFOmCnqEu92Fr1Mu4mxM.woff
15 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
15 ms
id
97 ms
Create
24 ms
GenerateIT
14 ms
think-king.com accessibility score
think-king.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
Page has valid source maps
think-king.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Think-king.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Think-king.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.
think-king.com
Open Graph data is detected on the main page of Think King. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: