Tools & Wizards About Us
imaginarium.com.tr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

imaginarium.com.tr

imaginarium.com.tr

Page Load Speed

4.9 sec in total

First Response

550 ms

Resources Loaded

3.7 sec

Page Rendered

642 ms

imaginarium.com.tr screenshot

About Website

Click here to check amazing Imaginarium content for Turkey. Otherwise, check out these important facts you probably never knew about imaginarium.com.tr

This domain may be for sale!

Visit imaginarium.com.tr

Key Findings

We analyzed Imaginarium.com.tr page load time and found that the first response time was 550 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

imaginarium.com.tr performance score

0

Network Requests Diagram

imaginarium.com.tr

550 ms

www.imaginarium.com.tr

1745 ms

custom.css

251 ms

brainsins.js

20 ms

analytics.js

34 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Imaginarium.com.tr, 30% (16 requests) were made to Static.imaginarium.es and 24% (13 requests) were made to Js.imaginarium.es. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Imaginarium.com.tr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (55%)

Content Size

2.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imaginarium.com.tr main page is 2.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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 173.3 kB

  • Original 200.8 kB
  • After minification 144.9 kB
  • After compression 27.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 55.9 kB, which is 28% 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 173.3 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 5.4 kB

  • Original 783.2 kB
  • After minification 777.8 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. Imaginarium images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 765.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 343.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 765.3 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 595.3 kB

  • Original 681.8 kB
  • After minification 681.0 kB
  • After compression 86.5 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. Imaginarium.com.tr needs all CSS files to be minified and compressed as it can save up to 595.3 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

51

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imaginarium.com.tr

imaginarium.com.tr

550 ms

www.imaginarium.com.tr

www.imaginarium.com.tr

1745 ms

custom.css

custom.css

251 ms

brainsins.js

brainsins.js

20 ms

analytics.js

analytics.js

34 ms

carruselHome1a_TR.jpg

carruselHome1a_TR.jpg

861 ms

carruselHome1b_TR.jpg

carruselHome1b_TR.jpg

845 ms

carruselHome2a_TR.jpg

carruselHome2a_TR.jpg

846 ms

carruselHome2b_TR.jpg

carruselHome2b_TR.jpg

843 ms

carruselHome3a_TR.jpg

carruselHome3a_TR.jpg

842 ms

carruselHome3b_TR.jpg

carruselHome3b_TR.jpg

845 ms

flecha-desplegable.svg

flecha-desplegable.svg

59 ms

lupa-buscador.svg

lupa-buscador.svg

60 ms

imaginariumCard_sombra.png

imaginariumCard_sombra.png

883 ms

tarjetaSocio.png

tarjetaSocio.png

809 ms

collect

collect

13 ms

collect

collect

70 ms

fontello.woff

fontello.woff

4 ms

jquery.bxslider.css

jquery.bxslider.css

40 ms

premio-european-retail-awards-2015.jpg

premio-european-retail-awards-2015.jpg

734 ms

tarjetasNuevo.png

tarjetasNuevo.png

14 ms

eb.resources.min.css

eb.resources.min.css

71 ms

empathy.resources.min.js

empathy.resources.min.js

95 ms

eb.resources.min.js

eb.resources.min.js

100 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

295 ms

modernizr.js

modernizr.js

265 ms

general.js

general.js

268 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

266 ms

cabecera.js

cabecera.js

274 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

268 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

268 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

270 ms

jquery.blockUI-2.66.0.js

jquery.blockUI-2.66.0.js

292 ms

jquery.lazyload.js

jquery.lazyload.js

273 ms

home.js

home.js

549 ms

cookies.js

cookies.js

291 ms

colbenson-jquery.js

colbenson-jquery.js

303 ms

magnific-popup.css

magnific-popup.css

265 ms

ping

ping

433 ms

ping

ping

454 ms

tracker.php

tracker.php

267 ms

bx_loader.gif

bx_loader.gif

94 ms

loading-140px.gif

loading-140px.gif

28 ms

ocuunuzla-birlikte-byyen-bisiklet_80617_3.jpg

ocuunuzla-birlikte-byyen-bisiklet_80617_3.jpg

715 ms

noFoto2.gif

noFoto2.gif

28 ms

oyuncak-bebek-beyaz-kiconico_47472_3.jpg

oyuncak-bebek-beyaz-kiconico_47472_3.jpg

431 ms

fire-engine-truck_76602_3.jpg

fire-engine-truck_76602_3.jpg

489 ms

elenceli-hayvanckl-piyano_80854_3.jpg

elenceli-hayvanckl-piyano_80854_3.jpg

687 ms

soru-cevap-oyunu_80842_3.jpg

soru-cevap-oyunu_80842_3.jpg

557 ms

controls3.png

controls3.png

256 ms

flechaSliderFichaIzq.svg

flechaSliderFichaIzq.svg

265 ms

flechaSliderFichaDcha.svg

flechaSliderFichaDcha.svg

273 ms

tracker.php

tracker.php

86 ms

trackBrainSinsData.json

trackBrainSinsData.json

188 ms

SEO Factors

imaginarium.com.tr SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imaginarium.com.tr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Imaginarium.com.tr 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

imaginarium.com.tr

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