Tools & Wizards About Us
component.se screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

component.se

För entusiaster av ljud och bild inom hifi & hemmabio! - Component

Page Load Speed

3.1 sec in total

First Response

223 ms

Resources Loaded

2.6 sec

Page Rendered

241 ms

component.se screenshot

About Website

Visit component.se now to see the best up-to-date Component content for Sweden and also check out these interesting facts you probably never knew about component.se

Component är en sajt som vill erbjuda ett mervärde genom att vara en samlingsplats för de som är intresserade av bild och ljud inom hifi och hemmabio.

Visit component.se

Key Findings

We analyzed Component.se page load time and found that the first response time was 223 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

component.se performance score

0

Network Requests Diagram

component.se

223 ms

www.component.se

1447 ms

style.css

104 ms

swfobject.js

224 ms

embed.js

207 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 86% of them (31 requests) were addressed to the original Component.se, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Static.hotjar.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Component.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.8 kB (46%)

Content Size

565.0 kB

After Optimization

304.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Component.se main page is 565.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. 25% of websites need less resources to load. Javascripts take 313.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 28.5 kB

  • Original 35.0 kB
  • After minification 26.0 kB
  • After compression 6.4 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 9.0 kB, which is 26% 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 28.5 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 16.0 kB

  • Original 213.3 kB
  • After minification 197.3 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. Component images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 213.8 kB

  • Original 313.3 kB
  • After minification 311.5 kB
  • After compression 99.6 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 213.8 kB or 68% of the original size.

CSS Optimization

-73%

Potential reduce by 2.5 kB

  • Original 3.5 kB
  • After minification 2.7 kB
  • After compression 928 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. Component.se needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (38%)

Requests Now

34

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Component. 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 as a result speed up the page load time.

Network Requests Diagram

component.se

component.se

223 ms

www.component.se

www.component.se

1447 ms

style.css

style.css

104 ms

swfobject.js

swfobject.js

224 ms

embed.js

embed.js

207 ms

tooltip.js

tooltip.js

221 ms

jquery-1.5.1.min.js

jquery-1.5.1.min.js

356 ms

banner.php

banner.php

403 ms

banner.php

banner.php

399 ms

hotjar-90684.js

hotjar-90684.js

92 ms

bg.gif

bg.gif

107 ms

component_header_logo.gif

component_header_logo.gif

107 ms

top-nav.gif

top-nav.gif

107 ms

weiss.jpg

weiss.jpg

208 ms

identity_thief.jpg

identity_thief.jpg

310 ms

duran-duran.jpg

duran-duran.jpg

310 ms

100-cover.jpg

100-cover.jpg

229 ms

div_news.gif

div_news.gif

279 ms

frost-cover.jpg

frost-cover.jpg

280 ms

playstation4.jpg

playstation4.jpg

310 ms

lovefilm.jpg

lovefilm.jpg

329 ms

frankenweenie.jpg

frankenweenie.jpg

385 ms

willow-bluray.jpg

willow-bluray.jpg

385 ms

hr-line.gif

hr-line.gif

410 ms

646_1170337447.jpg

646_1170337447.jpg

411 ms

spacer.gif

spacer.gif

410 ms

4624_1331653897.jpg

4624_1331653897.jpg

430 ms

1101_1314113470.jpg

1101_1314113470.jpg

491 ms

startpage_member_recruit.jpg

startpage_member_recruit.jpg

491 ms

modules-043c1e6abe660c48857202e419ff9d8a.js

modules-043c1e6abe660c48857202e419ff9d8a.js

26 ms

nsht-mksound-s300-980x120.jpg

nsht-mksound-s300-980x120.jpg

434 ms

sp_bg_2col.gif

sp_bg_2col.gif

334 ms

nsht-mksound-s300-980x240.jpg

nsht-mksound-s300-980x240.jpg

528 ms

analytics.js

analytics.js

16 ms

collect

collect

23 ms

visit-data

visit-data

197 ms

SEO Factors

component.se SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Component.se can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Component.se main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

component.se

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