Tools & Wizards About Us
interpar.de screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

interpar.de

Interpar die Firmen und Anbieter sowie Experten Spezialisten Suche

Page Load Speed

3.7 sec in total

First Response

320 ms

Resources Loaded

3.3 sec

Page Rendered

154 ms

interpar.de screenshot

About Website

Click here to check amazing Interpar content. Otherwise, check out these important facts you probably never knew about interpar.de

Interpar die Firmen und Anbieter Suche aus allen Branchen, Experten Spezialisten schneller und gezielt finden durch Empfehlungen von anderen Kunden

Visit interpar.de

Key Findings

We analyzed Interpar.de page load time and found that the first response time was 320 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

interpar.de performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value3,000 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.233

53/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

interpar.de

320 ms

www.interpar.de

560 ms

stylesheet_f8fd44c1b6.css

108 ms

fsnd.css

231 ms

cookiechoices.css

337 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 16% of them (11 requests) were addressed to the original Interpar.de, 19% (13 requests) were made to Pagead2.googlesyndication.com and 13% (9 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (663 ms) relates to the external source Piwik.fsnd.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.2 kB (10%)

Content Size

817.7 kB

After Optimization

733.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Interpar.de main page is 817.7 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. 55% of websites need less resources to load. Javascripts take 709.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 27.6 kB

  • Original 35.6 kB
  • After minification 34.7 kB
  • After compression 8.0 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 27.6 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 1.7 kB

  • Original 66.6 kB
  • After minification 64.9 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. Interpar images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 53.7 kB

  • Original 709.6 kB
  • After minification 709.4 kB
  • After compression 655.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. This website has mostly compressed JavaScripts.

CSS Optimization

-21%

Potential reduce by 1.2 kB

  • Original 5.9 kB
  • After minification 5.9 kB
  • After compression 4.7 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. Interpar.de needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (71%)

Requests Now

59

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

interpar.de

interpar.de

320 ms

www.interpar.de

www.interpar.de

560 ms

stylesheet_f8fd44c1b6.css

stylesheet_f8fd44c1b6.css

108 ms

fsnd.css

fsnd.css

231 ms

cookiechoices.css

cookiechoices.css

337 ms

adsbygoogle.js

adsbygoogle.js

175 ms

jquery.min.js

jquery.min.js

29 ms

fsnd.js

fsnd.js

345 ms

javascript_9a38f34785.js

javascript_9a38f34785.js

345 ms

cookiechoices.js

cookiechoices.js

369 ms

show_ads_impl.js

show_ads_impl.js

260 ms

fsnd.gif

fsnd.gif

108 ms

csm_fsnd_02_70170f769c.jpg

csm_fsnd_02_70170f769c.jpg

107 ms

csm_weltkugel_9c47639f1e.jpg

csm_weltkugel_9c47639f1e.jpg

108 ms

piwik.js

piwik.js

663 ms

zrt_lookup.html

zrt_lookup.html

77 ms

ads

ads

625 ms

ads

ads

563 ms

ads

ads

370 ms

ads

ads

522 ms

piwik.php

piwik.php

168 ms

gen_204

gen_204

96 ms

pixel

pixel

95 ms

12664907261908633388

12664907261908633388

117 ms

abg_lite.js

abg_lite.js

49 ms

omrhp.js

omrhp.js

83 ms

B31965939.393355372;dc_trk_aid=585290425;dc_trk_cid=214873224;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;gdpr=;gdpr_consent=;ltd=;tpsrc=cis;dc_tdv=1

B31965939.393355372;dc_trk_aid=585290425;dc_trk_cid=214873224;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;gdpr=;gdpr_consent=;ltd=;tpsrc=cis;dc_tdv=1

300 ms

Q12zgMmT.js

Q12zgMmT.js

112 ms

window_focus.js

window_focus.js

120 ms

qs_click_protection.js

qs_click_protection.js

133 ms

ufs_web_display.js

ufs_web_display.js

90 ms

icon.png

icon.png

39 ms

load_preloaded_resource.js

load_preloaded_resource.js

313 ms

abg_lite.js

abg_lite.js

294 ms

s

s

51 ms

ufs_web_display.js

ufs_web_display.js

70 ms

188a63c500db6a3aa7c42aa7d4186e28.js

188a63c500db6a3aa7c42aa7d4186e28.js

94 ms

reactive_library.js

reactive_library.js

280 ms

pixel

pixel

255 ms

pixel

pixel

255 ms

62bHydCX.html

62bHydCX.html

204 ms

css

css

121 ms

rum

rum

112 ms

bounce

bounce

129 ms

activeview

activeview

130 ms

6nBz8qVhgcmD6GxJa8R98i32RmIuiYHQQG15vc2mYdw.js

6nBz8qVhgcmD6GxJa8R98i32RmIuiYHQQG15vc2mYdw.js

87 ms

pixel

pixel

101 ms

pixel

pixel

100 ms

15d0cf978b3a1e6019f659c4e79f12e4.js

15d0cf978b3a1e6019f659c4e79f12e4.js

79 ms

7f032190f136c4d8e9a385e88120dc8d.js

7f032190f136c4d8e9a385e88120dc8d.js

81 ms

bbe3fbefe89164063f731512d72e756f.js

bbe3fbefe89164063f731512d72e756f.js

82 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

77 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

82 ms

pixel

pixel

141 ms

11512112508782714828

11512112508782714828

81 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

75 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

75 ms

gen_204

gen_204

108 ms

rum

rum

63 ms

activeview

activeview

81 ms

pixel

pixel

64 ms

pixel

pixel

64 ms

activeview

activeview

81 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

41 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

44 ms

pixel

pixel

36 ms

rum

rum

38 ms

setuid

setuid

35 ms

Accessibility Review

interpar.de accessibility score

97

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

interpar.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

interpar.de SEO score

92

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

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Interpar.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Interpar.de 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

interpar.de

Open Graph data is detected on the main page of Interpar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: