Tools & Wizards About Us
futurekid.com.kw screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

futurekid.com.kw

Future Kid - Home

Page Load Speed

7.7 sec in total

First Response

600 ms

Resources Loaded

6.4 sec

Page Rendered

656 ms

futurekid.com.kw screenshot

About Website

Visit futurekid.com.kw now to see the best up-to-date Future Kid content for Kuwait and also check out these interesting facts you probably never knew about futurekid.com.kw

Visit futurekid.com.kw

Key Findings

We analyzed Futurekid.com.kw page load time and found that the first response time was 600 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

futurekid.com.kw performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value21.1 s

0/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.122

84/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

futurekid.com.kw

600 ms

futurekid.com.kw

792 ms

ar

924 ms

vendors.min.css

365 ms

swiper.min.css

675 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 87% of them (47 requests) were addressed to the original Futurekid.com.kw, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Salesiq.zohopublic.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Futurekid.com.kw.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (15%)

Content Size

7.7 MB

After Optimization

6.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Futurekid.com.kw main page is 7.7 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. 35% of websites need less resources to load. Images take 6.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 36.9 kB

  • Original 42.4 kB
  • After minification 29.3 kB
  • After compression 5.5 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. This page needs HTML code to be minified as it can gain 13.1 kB, which is 31% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 36.9 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 70.8 kB

  • Original 6.3 MB
  • After minification 6.3 MB

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. Future Kid images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 475.9 kB

  • Original 653.8 kB
  • After minification 647.6 kB
  • After compression 177.9 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 475.9 kB or 73% of the original size.

CSS Optimization

-89%

Potential reduce by 566.9 kB

  • Original 634.3 kB
  • After minification 500.5 kB
  • After compression 67.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. Futurekid.com.kw needs all CSS files to be minified and compressed as it can save up to 566.9 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (40%)

Requests Now

50

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Future Kid. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

futurekid.com.kw

futurekid.com.kw

600 ms

futurekid.com.kw

futurekid.com.kw

792 ms

ar

ar

924 ms

vendors.min.css

vendors.min.css

365 ms

swiper.min.css

swiper.min.css

675 ms

bootstrap.css

bootstrap.css

1344 ms

bootstrap-extended.css

bootstrap-extended.css

861 ms

components.css

components.css

1056 ms

horizontal-menu.css

horizontal-menu.css

706 ms

ext-component-swiper.css

ext-component-swiper.css

538 ms

footer-rtl.css

footer-rtl.css

708 ms

style-rtl.css

style-rtl.css

842 ms

index-ar.css

index-ar.css

881 ms

logo-brand-ar.svg

logo-brand-ar.svg

886 ms

person-white.png

person-white.png

837 ms

main-logo-round-arabic.png

main-logo-round-arabic.png

1027 ms

left.png

left.png

890 ms

where_fun_never_ends_ar.svg

where_fun_never_ends_ar.svg

1069 ms

school-trip-ar.svg

school-trip-ar.svg

1003 ms

birthday-ar.svg

birthday-ar.svg

1059 ms

rentals-ar.svg

rentals-ar.svg

1063 ms

vendors.min.js

vendors.min.js

1995 ms

jquery.sticky.js

jquery.sticky.js

1188 ms

swiper.min.js

swiper.min.js

1403 ms

instafeed.min.js

instafeed.min.js

1274 ms

app-menu.js

app-menu.js

1275 ms

app.js

app.js

1335 ms

index.js

index.js

1356 ms

logo-brand.svg

logo-brand.svg

1409 ms

fb.svg

fb.svg

1419 ms

tw.svg

tw.svg

1499 ms

inst.svg

inst.svg

1524 ms

yt.svg

yt.svg

1576 ms

css

css

28 ms

css

css

45 ms

kw.svg

kw.svg

370 ms

landing_page_1.png

landing_page_1.png

1829 ms

offer_1.jpg

offer_1.jpg

1545 ms

offer_2.jpg

offer_2.jpg

660 ms

offer_3.jpg

offer_3.jpg

545 ms

e-gamers-galaxy.jpg

e-gamers-galaxy.jpg

2319 ms

vr.png

vr.png

2113 ms

group-rides.jpg

group-rides.jpg

1201 ms

arcades.jpg

arcades.jpg

1297 ms

sports-games.jpg

sports-games.jpg

1733 ms

table-games.jpg

table-games.jpg

1831 ms

bowling.png

bowling.png

2863 ms

driving-rides.jpg

driving-rides.jpg

2242 ms

prize-games.jpg

prize-games.jpg

2353 ms

widget

widget

360 ms

website

website

180 ms

floatbutton1_0uA5KIDjSJBNGPeiRDI3YtNcjWJ9mZsPq48NM5iMzp7_jWYVkIHbMtgrDX_xil60_.css

floatbutton1_0uA5KIDjSJBNGPeiRDI3YtNcjWJ9mZsPq48NM5iMzp7_jWYVkIHbMtgrDX_xil60_.css

93 ms

floatbutton1_ntOTzijfgIO2NxX8WMJch-kWe1HGIyvhXvC9ZYd6Bf-P-JdEDikGmCycyTnYqYia_.js

floatbutton1_ntOTzijfgIO2NxX8WMJch-kWe1HGIyvhXvC9ZYd6Bf-P-JdEDikGmCycyTnYqYia_.js

135 ms

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

21 ms

Accessibility Review

futurekid.com.kw accessibility score

81

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

futurekid.com.kw best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

futurekid.com.kw SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    AR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futurekid.com.kw 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 Arabic language. Our system also found out that Futurekid.com.kw 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.

Social Sharing Optimization

futurekid.com.kw

Open Graph description is not detected on the main page of Future Kid. 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: