Tools & Wizards About Us
foobarblog.net screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 53% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

foobarblog.net

Der Foobar Blog | Webentwicklung mal ganz einfach!

Page Load Speed

3.6 sec in total

First Response

647 ms

Resources Loaded

2.5 sec

Page Rendered

453 ms

foobarblog.net screenshot

About Website

Visit foobarblog.net now to see the best up-to-date Foobar Blog content for Germany and also check out these interesting facts you probably never knew about foobarblog.net

Der Blog vermittelt nützliche Tipps, Anregungen und Techniken zur Webgestaltung und -programmierung. Die verwendeten (Programmier-) Sprachen sind HTML, CSS, JavaScript, PHP und MySQL. Die Hauptzielgru...

Visit foobarblog.net

Key Findings

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

Performance Metrics

foobarblog.net performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

92/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value2,230 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

foobarblog.net

647 ms

xmscache_eedc8301910eaa11c867579574a2c066.css

208 ms

xmscache_09c1e1bd10d1eb0257084f9143c6bad2.js

397 ms

platform.js

63 ms

adsbygoogle.js

18 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 12% of them (6 requests) were addressed to the original Foobarblog.net, 15% (8 requests) were made to Apis.google.com and 10% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (755 ms) relates to the external source Static.flattr.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 278.6 kB (33%)

Content Size

847.2 kB

After Optimization

568.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foobarblog.net main page is 847.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. 65% of websites need less resources to load. Images take 422.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 34.5 kB

  • Original 44.0 kB
  • After minification 35.2 kB
  • After compression 9.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 8.8 kB, which is 20% 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 34.5 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 5.1 kB

  • Original 422.0 kB
  • After minification 417.0 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. Foobar Blog images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 162.4 kB

  • Original 283.8 kB
  • After minification 208.1 kB
  • After compression 121.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 162.4 kB or 57% of the original size.

CSS Optimization

-79%

Potential reduce by 76.7 kB

  • Original 97.4 kB
  • After minification 74.4 kB
  • After compression 20.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. Foobarblog.net needs all CSS files to be minified and compressed as it can save up to 76.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (56%)

Requests Now

48

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foobarblog.net

foobarblog.net

647 ms

xmscache_eedc8301910eaa11c867579574a2c066.css

xmscache_eedc8301910eaa11c867579574a2c066.css

208 ms

xmscache_09c1e1bd10d1eb0257084f9143c6bad2.js

xmscache_09c1e1bd10d1eb0257084f9143c6bad2.js

397 ms

platform.js

platform.js

63 ms

adsbygoogle.js

adsbygoogle.js

18 ms

analytics.js

analytics.js

17 ms

body_bg.jpg

body_bg.jpg

741 ms

stage.jpg

stage.jpg

293 ms

poweredByDieBeidenDark.png

poweredByDieBeidenDark.png

291 ms

sdk.js

sdk.js

24 ms

collect

collect

55 ms

ca-pub-5621774507376455.js

ca-pub-5621774507376455.js

66 ms

zrt_lookup.html

zrt_lookup.html

60 ms

show_ads_impl.js

show_ads_impl.js

125 ms

363 ms

widgets.js

widgets.js

151 ms

xd_arbiter.php

xd_arbiter.php

139 ms

xd_arbiter.php

xd_arbiter.php

153 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

123 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

122 ms

fastbutton

fastbutton

178 ms

ads

ads

227 ms

osd.js

osd.js

43 ms

ads

ads

230 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

142 ms

postmessageRelay

postmessageRelay

64 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

14 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

13 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

29 ms

323 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

20 ms

rpc:shindig_random.js

rpc:shindig_random.js

37 ms

like.php

like.php

337 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.de.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.de.html

43 ms

css

css

114 ms

m_js_controller.js

m_js_controller.js

54 ms

abg.js

abg.js

65 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

93 ms

6684881834272372724

6684881834272372724

50 ms

x_button_blue2.png

x_button_blue2.png

25 ms

s

s

22 ms

favicon

favicon

67 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

28 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

2 ms

jot

jot

109 ms

4A-myfZX6oDr9CtSTkTGig.ttf

4A-myfZX6oDr9CtSTkTGig.ttf

33 ms

cloudflare.min.js

cloudflare.min.js

8 ms

button.css

button.css

755 ms

button.js

button.js

644 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

32 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

13 ms

Accessibility Review

foobarblog.net accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

foobarblog.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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

foobarblog.net SEO score

93

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 Foobarblog.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 Foobarblog.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

foobarblog.net

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