Tools & Wizards About Us
vimu.info screenshot

Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

vimu.info

Entdecker

Page Load Speed

1.5 sec in total

First Response

104 ms

Resources Loaded

1.2 sec

Page Rendered

206 ms

vimu.info screenshot

About Website

Visit vimu.info now to see the best up-to-date Vimu content for Denmark and also check out these interesting facts you probably never knew about vimu.info

dänisch - deutsche geschichte der moderne im internet: aus politik, gesellschaft, kultur und mehr.

Visit vimu.info

Key Findings

We analyzed Vimu.info page load time and found that the first response time was 104 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

vimu.info performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

general_01.jsp

104 ms

swfobject.js

96 ms

newstyle.css

188 ms

fontstyleswitcher.js

189 ms

urchin.js

20 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 93% of them (28 requests) were addressed to the original Vimu.info, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (465 ms) belongs to the original domain Vimu.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 31.5 kB (29%)

Content Size

107.9 kB

After Optimization

76.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vimu.info main page is 107.9 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. 15% of websites need less resources to load. Images take 62.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 17.6 kB

  • Original 22.2 kB
  • After minification 16.9 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. This page needs HTML code to be minified as it can gain 5.2 kB, which is 24% 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 17.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 122 B

  • Original 62.0 kB
  • After minification 61.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. Vimu images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 7.7 kB

  • Original 16.1 kB
  • After minification 14.7 kB
  • After compression 8.4 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 7.7 kB or 48% of the original size.

CSS Optimization

-81%

Potential reduce by 6.1 kB

  • Original 7.6 kB
  • After minification 5.9 kB
  • After compression 1.5 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. Vimu.info needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

29

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vimu. 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

general_01.jsp

general_01.jsp

104 ms

swfobject.js

swfobject.js

96 ms

newstyle.css

newstyle.css

188 ms

fontstyleswitcher.js

fontstyleswitcher.js

189 ms

urchin.js

urchin.js

20 ms

__utm.gif

__utm.gif

12 ms

logo_vertical.gif

logo_vertical.gif

96 ms

top_general.gif

top_general.gif

95 ms

dk.gif

dk.gif

167 ms

font_smaller.gif

font_smaller.gif

185 ms

font_standard.gif

font_standard.gif

186 ms

font_bigger.gif

font_bigger.gif

184 ms

barlach.jpg

barlach.jpg

190 ms

samarbejde.jpg

samarbejde.jpg

189 ms

36_2_2_fo_1890-1918.jpg

36_2_2_fo_1890-1918.jpg

256 ms

karikatur.jpg

karikatur.jpg

367 ms

badezeit.jpg

badezeit.jpg

275 ms

denkmal.jpg

denkmal.jpg

276 ms

sdu_logo.gif

sdu_logo.gif

282 ms

unilogo.gif

unilogo.gif

282 ms

fhkiellogo.gif

fhkiellogo.gif

349 ms

logo_eu.gif

logo_eu.gif

366 ms

tourist.gif

tourist.gif

366 ms

pupils.gif

pupils.gif

374 ms

teacher.gif

teacher.gif

375 ms

researcher.gif

researcher.gif

439 ms

kids.gif

kids.gif

456 ms

arrow_faq.gif

arrow_faq.gif

456 ms

print.gif

print.gif

457 ms

send.gif

send.gif

465 ms

Accessibility Review

vimu.info accessibility score

76

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.

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

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

Links do not have a discernible name

Best Practices

vimu.info best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

vimu.info SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    DE

  • 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 Vimu.info can be misinterpreted by Google and other search engines. Our service has detected that German 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 Vimu.info 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

vimu.info

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