Tools & Wizards About Us
intimus.eu screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

intimus.eu

intimus | The Shredder Company

Page Load Speed

5.6 sec in total

First Response

474 ms

Resources Loaded

4.9 sec

Page Rendered

202 ms

intimus.eu screenshot

About Website

Click here to check amazing Intimus content. Otherwise, check out these important facts you probably never knew about intimus.eu

Secure your data with intimus: advanced solutions for document and media shredding ensure top security and reliability, offering peace of mind.

Visit intimus.eu

Key Findings

We analyzed Intimus.eu page load time and found that the first response time was 474 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

intimus.eu performance score

0

Network Requests Diagram

intimus.eu

474 ms

www.intimus.eu

2855 ms

baw_language_selector.php

227 ms

all.css

220 ms

screen.css

332 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 78% of them (43 requests) were addressed to the original Intimus.eu, 9% (5 requests) were made to Translate.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Intimus.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 312.5 kB (39%)

Content Size

807.0 kB

After Optimization

494.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intimus.eu main page is 807.0 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. 35% of websites need less resources to load. Javascripts take 402.8 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 19.6 kB

  • Original 26.7 kB
  • After minification 26.7 kB
  • After compression 7.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 19.6 kB or 73% of the original size.

Image Optimization

-11%

Potential reduce by 37.8 kB

  • Original 351.9 kB
  • After minification 314.1 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. Obviously, Intimus needs image optimization as it can save up to 37.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 237.6 kB

  • Original 402.8 kB
  • After minification 372.4 kB
  • After compression 165.2 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 237.6 kB or 59% of the original size.

CSS Optimization

-69%

Potential reduce by 17.6 kB

  • Original 25.6 kB
  • After minification 24.6 kB
  • After compression 8.0 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. Intimus.eu needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (57%)

Requests Now

53

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intimus.eu

intimus.eu

474 ms

www.intimus.eu

www.intimus.eu

2855 ms

baw_language_selector.php

baw_language_selector.php

227 ms

all.css

all.css

220 ms

screen.css

screen.css

332 ms

37022b7764713580ba65f11ab9932bc7_bawjs.js

37022b7764713580ba65f11ab9932bc7_bawjs.js

678 ms

variationcompare.js

variationcompare.js

223 ms

add2cart.js

add2cart.js

222 ms

vertriebskarte.js

vertriebskarte.js

329 ms

changedetailpic.js

changedetailpic.js

340 ms

element.js

element.js

32 ms

widgets.js

widgets.js

5 ms

tabber.js

tabber.js

238 ms

dropdownmenu.js

dropdownmenu.js

238 ms

fixedtooltip.js

fixedtooltip.js

333 ms

posmenu.js

posmenu.js

336 ms

youtube_32x32.png

youtube_32x32.png

12 ms

2779_19x19_i_icon_printpage.gif

2779_19x19_i_icon_printpage.gif

122 ms

3004_19x19_i_icon_back.gif

3004_19x19_i_icon_back.gif

123 ms

7156_54x173_intimus_logo_new_small.png

7156_54x173_intimus_logo_new_small.png

123 ms

6304_250x690_Kopf_Grafik_int_1912.jpg

6304_250x690_Kopf_Grafik_int_1912.jpg

555 ms

4016_200x141_intimus120mDeco.jpg

4016_200x141_intimus120mDeco.jpg

224 ms

3675_25x116_intimus_pro.jpg

3675_25x116_intimus_pro.jpg

329 ms

60_143x200_intimus1585.jpg

60_143x200_intimus1585.jpg

329 ms

3676_25x139_intimus_power.jpg

3676_25x139_intimus_power.jpg

444 ms

3898_150x200_intimus_pacmaster_S_02_web.jpg

3898_150x200_intimus_pacmaster_S_02_web.jpg

224 ms

3674_25x152_intimus_recycle.jpg

3674_25x152_intimus_recycle.jpg

554 ms

4018_150x101_intimus_1000_02.jpg

4018_150x101_intimus_1000_02.jpg

444 ms

3678_25x144_intimus_crypto.jpg

3678_25x144_intimus_crypto.jpg

661 ms

6410_52x50_AFCEA_CorporateMember_LOGO.jpg

6410_52x50_AFCEA_CorporateMember_LOGO.jpg

555 ms

2842_30x126_flogo_martinyale_international.gif

2842_30x126_flogo_martinyale_international.gif

553 ms

2791_30x144_flogo_martinyale.gif

2791_30x144_flogo_martinyale.gif

557 ms

2792_30x159_flogo_papermonster.gif

2792_30x159_flogo_papermonster.gif

662 ms

3030_11x16_flaggs_de.gif

3030_11x16_flaggs_de.gif

664 ms

3031_11x16_flaggs_gb.gif

3031_11x16_flaggs_gb.gif

665 ms

2781_19x19_i_icon_sitemap.gif

2781_19x19_i_icon_sitemap.gif

667 ms

2783_19x19_i_icon_imprint.gif

2783_19x19_i_icon_imprint.gif

668 ms

2780_19x19_i_icon_recommend.gif

2780_19x19_i_icon_recommend.gif

773 ms

2782_19x19_i_icon_toplink.gif

2782_19x19_i_icon_toplink.gif

774 ms

w_body.gif

w_body.gif

770 ms

w_head.gif

w_head.gif

772 ms

w_searchinput.gif

w_searchinput.gif

773 ms

w_menu.gif

w_menu.gif

771 ms

w_menu2.gif

w_menu2.gif

870 ms

w_mainend.gif

w_mainend.gif

871 ms

translateelement.css

translateelement.css

60 ms

main.js

main.js

78 ms

element_main.js

element_main.js

37 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

13 ms

translate_24dp.png

translate_24dp.png

21 ms

l

l

44 ms

cleardot.gif

cleardot.gif

33 ms

te_ctrl3.gif

te_ctrl3.gif

11 ms

print.css

print.css

112 ms

SEO Factors

intimus.eu SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intimus.eu 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 Intimus.eu 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

intimus.eu

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