Tools & Wizards About Us
blog.formativ.net screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

blog.formativ.net

Blog Archive - formativ.net - Ihre Internetagentur in Frankfurt und Karlsruhe

Page Load Speed

4.7 sec in total

First Response

337 ms

Resources Loaded

2.9 sec

Page Rendered

1.4 sec

blog.formativ.net screenshot

About Website

Click here to check amazing Blog Formativ content for Germany. Otherwise, check out these important facts you probably never knew about blog.formativ.net

Entdecke spannende Themen rund um das Internet, Webdesign, Webentwicklung, Programmierung, Apps und Insights aus unserem Agenturalltag.

Visit blog.formativ.net

Key Findings

We analyzed Blog.formativ.net page load time and found that the first response time was 337 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

blog.formativ.net performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.193

63/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

blog.formativ.net

337 ms

blog.formativ.net

438 ms

680 ms

matomo.js

746 ms

style.min.css

320 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original Blog.formativ.net, 86% (24 requests) were made to Formativ.net and 7% (2 requests) were made to Get.formativ.net. The less responsive or slowest element that took the longest time to load (945 ms) relates to the external source Formativ.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 896.1 kB (41%)

Content Size

2.2 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.formativ.net main page is 2.2 MB. 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 69.3 kB

  • Original 83.6 kB
  • After minification 71.5 kB
  • After compression 14.3 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 12.1 kB, which is 15% 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 69.3 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 33.4 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. Blog Formativ images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 315.3 kB

  • Original 470.1 kB
  • After minification 470.1 kB
  • After compression 154.8 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 315.3 kB or 67% of the original size.

CSS Optimization

-88%

Potential reduce by 478.0 kB

  • Original 541.2 kB
  • After minification 540.7 kB
  • After compression 63.2 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. Blog.formativ.net needs all CSS files to be minified and compressed as it can save up to 478.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (28%)

Requests Now

25

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.formativ.net

blog.formativ.net

337 ms

blog.formativ.net

blog.formativ.net

438 ms

680 ms

matomo.js

matomo.js

746 ms

style.min.css

style.min.css

320 ms

style.css

style.css

306 ms

enlighterjs.min.css

enlighterjs.min.css

523 ms

theme.1.css

theme.1.css

843 ms

custom.css

custom.css

324 ms

jquery.min.js

jquery.min.js

532 ms

lazyload.min.js

lazyload.min.js

404 ms

d76c4920b05d4de9a51f64d0d3a07d5b.js

d76c4920b05d4de9a51f64d0d3a07d5b.js

634 ms

logo-65e5d309.png

logo-65e5d309.png

423 ms

FXT26281_klein-scaled-780fee96.jpeg

FXT26281_klein-scaled-780fee96.jpeg

945 ms

wordpress-linkvorschau-ausschalten-395d8cdd.webp

wordpress-linkvorschau-ausschalten-395d8cdd.webp

944 ms

matomo.php

matomo.php

597 ms

joomla_org-0db29b6c.webp

joomla_org-0db29b6c.webp

109 ms

1907-wp-fehler-vermeiden-66448595.jpeg

1907-wp-fehler-vermeiden-66448595.jpeg

227 ms

geschichte-internet-webentwicklung-e7f11f81.webp

geschichte-internet-webentwicklung-e7f11f81.webp

106 ms

cookie-756601_1920-78fe00a4.jpeg

cookie-756601_1920-78fe00a4.jpeg

520 ms

2403-digitalisierung-automatisierung-webentwicklung-819c42ac.webp

2403-digitalisierung-automatisierung-webentwicklung-819c42ac.webp

116 ms

2402-pwa-ios-app-programmierung-a981091e.webp

2402-pwa-ios-app-programmierung-a981091e.webp

116 ms

2310-Joomla5--db62819f.jpeg

2310-Joomla5--db62819f.jpeg

226 ms

2309-JoomlaDay2023-formativ_net-c536acd0.jpeg

2309-JoomlaDay2023-formativ_net-c536acd0.jpeg

219 ms

JUG-FFM-d4737d02.webp

JUG-FFM-d4737d02.webp

226 ms

call.svg

call.svg

222 ms

sms.svg

sms.svg

310 ms

briefcase.svg

briefcase.svg

324 ms

Accessibility Review

blog.formativ.net accessibility score

95

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

Links do not have a discernible name

Best Practices

blog.formativ.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

blog.formativ.net SEO score

100

Search Engine Optimization Advices

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 Blog.formativ.net 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 Blog.formativ.net 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

blog.formativ.net

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