Tools & Wizards About Us
fragen.de screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fragen.de

fragen.de - This website is for sale! - fragen Resources and Information.

Page Load Speed

2.7 sec in total

First Response

525 ms

Resources Loaded

1.8 sec

Page Rendered

367 ms

fragen.de screenshot

About Website

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

This website is for sale! fragen.de is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, fragen.de has it all...

Visit fragen.de

Key Findings

We analyzed Fragen.de page load time and found that the first response time was 525 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

fragen.de performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.219

57/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

fragen.de

525 ms

fragen.css

199 ms

ajax_def.js

205 ms

ajax_reg.js

219 ms

reflection.js

214 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 38% of them (16 requests) were addressed to the original Fragen.de, 14% (6 requests) were made to Primary.bannerwerbung.net and 12% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (811 ms) belongs to the original domain Fragen.de.

Page Optimization Overview & Recommendations

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

Content Size

588.2 kB

After Optimization

361.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fragen.de main page is 588.2 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. 40% of websites need less resources to load. Images take 445.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 22.1 kB

  • Original 26.6 kB
  • After minification 24.8 kB
  • After compression 4.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. 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 22.1 kB or 83% of the original size.

Image Optimization

-31%

Potential reduce by 137.4 kB

  • Original 445.8 kB
  • After minification 308.4 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, Fragen needs image optimization as it can save up to 137.4 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 55.2 kB

  • Original 101.3 kB
  • After minification 97.9 kB
  • After compression 46.1 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 55.2 kB or 55% of the original size.

CSS Optimization

-82%

Potential reduce by 11.8 kB

  • Original 14.5 kB
  • After minification 12.2 kB
  • After compression 2.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. Fragen.de needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (61%)

Requests Now

41

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fragen.de

fragen.de

525 ms

fragen.css

fragen.css

199 ms

ajax_def.js

ajax_def.js

205 ms

ajax_reg.js

ajax_reg.js

219 ms

reflection.js

reflection.js

214 ms

spcjs.php

spcjs.php

382 ms

analytics.js

analytics.js

5 ms

linkid.js

linkid.js

8 ms

collect

collect

3 ms

collect

collect

60 ms

spc.php

spc.php

124 ms

fl.js

fl.js

193 ms

bg3.jpg

bg3.jpg

811 ms

headerbg.jpg

headerbg.jpg

154 ms

header2.jpg

header2.jpg

554 ms

frage_user.gif

frage_user.gif

150 ms

frage_time.gif

frage_time.gif

139 ms

frage_comments.gif

frage_comments.gif

240 ms

frage_reply.gif

frage_reply.gif

240 ms

leer.gif

leer.gif

241 ms

show_ads.js

show_ads.js

5 ms

ag.php

ag.php

130 ms

lg.php

lg.php

142 ms

ca-pub-2759013351860096.js

ca-pub-2759013351860096.js

33 ms

zrt_lookup.html

zrt_lookup.html

32 ms

show_ads_impl.js

show_ads_impl.js

48 ms

ads

ads

219 ms

osd.js

osd.js

61 ms

loginbg.gif

loginbg.gif

266 ms

input_suchen.jpg

input_suchen.jpg

157 ms

go.gif

go.gif

173 ms

lg.php

lg.php

108 ms

ads

ads

175 ms

ads

ads

159 ms

13226038036456950958

13226038036456950958

131 ms

abg.js

abg.js

48 ms

m_js_controller.js

m_js_controller.js

73 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

121 ms

12602525208917597686

12602525208917597686

95 ms

s

s

56 ms

x_button_blue2.png

x_button_blue2.png

51 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

10 ms

Accessibility Review

fragen.de accessibility score

63

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.

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

<frame> or <iframe> elements do not have a title

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

fragen.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fragen.de SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    DE

  • Encoding

    ISO-8859-1

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

fragen.de

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