Tools & Wizards About Us
indat.de screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

indat.de

indat

Page Load Speed

2.7 sec in total

First Response

289 ms

Resources Loaded

1.7 sec

Page Rendered

715 ms

indat.de screenshot

About Website

Welcome to indat.de homepage info - get ready to check Indat best content right away, or after learning these important things about indat.de

Visit indat.de

Key Findings

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

Performance Metrics

indat.de performance score

0

Network Requests Diagram

indat.de

289 ms

home.htm

103 ms

top.htm

97 ms

hauptnav.htm

203 ms

left.htm

205 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that all of those requests were addressed to Indat.de and no external sources were called. The less responsive or slowest element that took the longest time to load (684 ms) belongs to the original domain Indat.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.6 kB (6%)

Content Size

499.2 kB

After Optimization

470.6 kB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-47%

Potential reduce by 509 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 580 B

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 509 B or 47% of the original size.

Image Optimization

-5%

Potential reduce by 25.9 kB

  • Original 495.6 kB
  • After minification 469.7 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. Indat images are well optimized though.

CSS Optimization

-86%

Potential reduce by 2.2 kB

  • Original 2.5 kB
  • After minification 2.1 kB
  • After compression 350 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. Indat.de needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (49%)

Requests Now

47

After Optimization

24

  • AJAX
  • Images
  • CSS

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

Network Requests Diagram

indat.de

indat.de

289 ms

home.htm

home.htm

103 ms

top.htm

top.htm

97 ms

hauptnav.htm

hauptnav.htm

203 ms

left.htm

left.htm

205 ms

news.htm

news.htm

302 ms

foto-top.gif

foto-top.gif

207 ms

clear_dot.gif

clear_dot.gif

100 ms

lin_g.gif

lin_g.gif

97 ms

profil.gif

profil.gif

193 ms

new_down.gif

new_down.gif

196 ms

service.gif

service.gif

204 ms

shop.gif

shop.gif

203 ms

treiber.gif

treiber.gif

209 ms

schnaepp.gif

schnaepp.gif

220 ms

kontakt.gif

kontakt.gif

287 ms

impress.gif

impress.gif

282 ms

lin_gq.gif

lin_gq.gif

293 ms

home.gif

home.gif

295 ms

schriften.css

schriften.css

302 ms

Miniserver.jpg

Miniserver.jpg

321 ms

rot.gif

rot.gif

366 ms

asuslogo.jpg

asuslogo.jpg

461 ms

windows_10_compatible.jpg

windows_10_compatible.jpg

387 ms

ASUS_Garantie.JPG

ASUS_Garantie.JPG

389 ms

ASUS_P550.jpg

ASUS_P550.jpg

399 ms

ASUS_X751.jpg

ASUS_X751.jpg

407 ms

indatlogo1.jpg

indatlogo1.jpg

461 ms

Antec_NSK3100.jpg

Antec_NSK3100.jpg

488 ms

ASUS_N552.jpg

ASUS_N552.jpg

490 ms

toshiba-logo-1.jpg

toshiba-logo-1.jpg

499 ms

Toshiba_Gold.jpg

Toshiba_Gold.jpg

509 ms

Toshiba-a40-c.jpg

Toshiba-a40-c.jpg

554 ms

MS-Tech-CA-0186-U3.jpg

MS-Tech-CA-0186-U3.jpg

555 ms

intel-logo.jpg

intel-logo.jpg

587 ms

Intel_Stick.jpg

Intel_Stick.jpg

590 ms

ASUS_UX305.jpg

ASUS_UX305.jpg

513 ms

lin_dg_a.gif

lin_dg_a.gif

343 ms

news.gif

news.gif

383 ms

ser_down.gif

ser_down.gif

383 ms

sho_down.gif

sho_down.gif

421 ms

tre_down.gif

tre_down.gif

423 ms

sch_down.gif

sch_down.gif

433 ms

kon_down.gif

kon_down.gif

443 ms

pro_down.gif

pro_down.gif

476 ms

lin_dgq_a.gif

lin_dgq_a.gif

463 ms

hom_down.gif

hom_down.gif

506 ms

imp_down.gif

imp_down.gif

508 ms

miniserver.jpg

miniserver.jpg

684 ms

asus_garantie.jpg

asus_garantie.jpg

428 ms

asus_p550.jpg

asus_p550.jpg

445 ms

asus_x751.jpg

asus_x751.jpg

625 ms

antec_nsk3100.jpg

antec_nsk3100.jpg

505 ms

asus_n552.jpg

asus_n552.jpg

504 ms

toshiba_gold.jpg

toshiba_gold.jpg

408 ms

toshiba-a40-c.jpg

toshiba-a40-c.jpg

383 ms

ms-tech-ca-0186-u3.jpg

ms-tech-ca-0186-u3.jpg

463 ms

intel_stick.jpg

intel_stick.jpg

442 ms

asus_ux305.jpg

asus_ux305.jpg

494 ms

Accessibility Review

indat.de accessibility score

33

Accessibility Issues

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

indat.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

indat.de SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indat.de 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 Indat.de main page’s claimed encoding is . 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

indat.de

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