7.6 sec in total
1.8 sec
5.1 sec
654 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 1.8 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
think-king.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value7.1 s
5/100
25%
Value38.8 s
0/100
10%
Value45,960 ms
0/100
30%
Value0.312
37/100
15%
Value59.0 s
0/100
10%
1820 ms
191 ms
82 ms
128 ms
150 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 86% of them (103 requests) were addressed to the original Think-king.com, 5% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Think-king.com.
Page size can be reduced by 179.5 kB (25%)
712.3 kB
532.8 kB
In fact, the total size of Think-king.com main page is 712.3 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. 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 243.9 kB which makes up the majority of the site volume.
Potential reduce by 177.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 177.6 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 583 B
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 1.3 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. Think-king.com has all CSS files already compressed.
Number of requests can be reduced by 107 (96%)
112
5
The browser has sent 112 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 61 to 1 for JavaScripts and from 48 to 1 for CSS and as a result speed up the page load time.
think-king.com
1820 ms
css
191 ms
vtprd-front-end-min.css
82 ms
style.min.css
128 ms
theme.min.css
150 ms
autoptimize_single_ee78f26525b08d4e372b92a1a3ed1d26.php
188 ms
autoptimize_single_8d1c626db828d6d0cf8fbda06adadb4d.php
160 ms
style.min.css
102 ms
style.min.css
145 ms
style.min.css
155 ms
style.min.css
181 ms
autoptimize_single_e6fae855021a88a0067fcc58121c594f.php
377 ms
autoptimize_single_1ddf23fcfd1b2941c456ce01da8180a6.php
195 ms
autoptimize_single_979b8b56e801469d95453055366ef54c.php
237 ms
autoptimize_single_11ef7ca744675858bb94aa8eb86a2067.php
234 ms
styles.min.css
197 ms
autoptimize_single_8e2f6ed38d662dc1a91f4277877ae39c.php
281 ms
autoptimize_single_f38b2db10e01b1572732a3191d538707.php
265 ms
main.min.css
215 ms
dashicons.min.css
228 ms
animate.min.css
272 ms
fresco.min.css
298 ms
easyzoom.min.css
281 ms
autoptimize_single_7a162ca35a696ba5d54949e3c7c43887.php
371 ms
swiper.min.css
302 ms
page-in-out.min.css
281 ms
style.min.css
366 ms
styles.min.css
307 ms
autoptimize_single_155afb7d5ca08b441d97a0ae11e0e26b.php
419 ms
misc.min.css
354 ms
social-media.min.css
355 ms
autoptimize_single_c6107b72b9ab8eefe4a44670f0009799.php
416 ms
social-sharing.min.css
414 ms
autoptimize_single_9ed6c04ed63c185986d33e9907a0e704.php
425 ms
style.min.css
354 ms
js_composer.min.css
358 ms
autoptimize_single_9c23e4e35fb83d64c7f8841816ef76ac.php
476 ms
45862fdbc0.js
200 ms
js
204 ms
api.js
166 ms
iframe_api
165 ms
v652eace1692a40cfa3763df669d7439c1639079717194
310 ms
autoptimize_single_bf9d2ad2b49f59a130829909784c447d.php
441 ms
animate.min.css
370 ms
vc_carousel.min.css
354 ms
nprogress.min.js
331 ms
jquery.min.js
317 ms
jquery-migrate.min.js
387 ms
slider.min.js
345 ms
jquery.blockUI.min.js
319 ms
add-to-cart.min.js
304 ms
autoptimize_single_787fe4f547a6cb7f4ce4934641085910.php
333 ms
autoptimize_single_01d8c4d6762632dbdb7c1a28ce147933.php
315 ms
lazysizes.min.js
300 ms
wp-polyfill.min.js
279 ms
autoptimize_single_cfb428c02811f0cbe515d5f3dca61de6.php
288 ms
js.cookie.min.js
273 ms
woocommerce.min.js
243 ms
cart-fragments.min.js
240 ms
autoptimize_single_471f4b3ef0440a7665b9da213bb56631.php
244 ms
autoptimize_single_a0ebffd48dfe176e23c709dfaaff3e58.php
247 ms
photoswipe.min.js
236 ms
photoswipe-ui-default.min.js
215 ms
slick.min.js
216 ms
hoverIntent.min.js
156 ms
underscore.min.js
158 ms
wp-util.min.js
162 ms
hooks.min.js
154 ms
main.min.js
157 ms
add-to-cart-variation.min.js
154 ms
TweenMax.min.js
166 ms
main.min.js
154 ms
custom-notifications.min.js
109 ms
autoptimize_single_6a0e8318d42803736d2fafcc12238026.php
112 ms
css
105 ms
foundation.min.js
136 ms
isotope.pkgd.min.js
104 ms
fresco.min.js
101 ms
imagesloaded.min.js
128 ms
easyzoom.min.js
96 ms
jquery.touchSwipe.min.js
120 ms
swiper.min.js
99 ms
select2.full.min.js
100 ms
jquery.stellar.min.js
85 ms
velocity.min.js
110 ms
styles.css
105 ms
styles.css
112 ms
styles.css
100 ms
styles.css
106 ms
styles.css
104 ms
styles.css
100 ms
styles.css
107 ms
js_composer_front.min.js
99 ms
scripts.min.js
98 ms
autoptimize_single_7f4902c5562b990540d6a4d4cd7e66cf.php
386 ms
portfolio.min.js
98 ms
wp-embed.min.js
97 ms
vc-waypoints.min.js
96 ms
transition.min.js
378 ms
vc_carousel.min.js
376 ms
ThinkKing-hooks-stroller.jpg
379 ms
analytics.js
625 ms
S6uyw4BMUTPHjx4wWw.ttf
433 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
679 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
914 ms
S6u_w4BMUTPHjxsI5wq_Gwfo.ttf
914 ms
S6u8w4BMUTPHjxsAXC-v.ttf
915 ms
S6u_w4BMUTPHjxsI9w2_Gwfo.ttf
918 ms
Shopkeeper-Icon-Font.ttf
268 ms
autoptimize_single_456663a286a204386735fd775542a59e.php
201 ms
ThinkKing_logo_web.svg
484 ms
wp-polyfill-fetch.min.js
157 ms
wp-polyfill-dom-rect.min.js
162 ms
wp-polyfill-url.min.js
161 ms
wp-polyfill-formdata.min.js
185 ms
wp-polyfill-element-closest.min.js
181 ms
wp-polyfill-object-fit.min.js
154 ms
collect
517 ms
recaptcha__en.js
325 ms
www-widgetapi.js
55 ms
think-king.com 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
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
think-king.com 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
Page has valid source maps
think-king.com 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
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: