6.1 sec in total
597 ms
4.8 sec
706 ms
Click here to check amazing Oldenburger Lokalteil content. Otherwise, check out these important facts you probably never knew about oldenburger-lokalteil.de
Der Oldenburger Lokalteil ist ein unabhängiges Onlinemagazin für Oldenburg.
Visit oldenburger-lokalteil.deWe analyzed Oldenburger-lokalteil.de page load time and found that the first response time was 597 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
oldenburger-lokalteil.de performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value0.9 s
100/100
25%
Value0.9 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.9 s
100/100
10%
597 ms
1220 ms
301 ms
201 ms
205 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 78% of them (98 requests) were addressed to the original Oldenburger-lokalteil.de, 8% (10 requests) were made to Static.xx.fbcdn.net and 6% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Oldenburger-lokalteil.de.
Page size can be reduced by 890.6 kB (38%)
2.4 MB
1.5 MB
In fact, the total size of Oldenburger-lokalteil.de main page is 2.4 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 112.2 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 112.2 kB or 82% of the original size.
Potential reduce by 51.5 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. Oldenburger Lokalteil images are well optimized though.
Potential reduce by 576.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 576.1 kB or 77% of the original size.
Potential reduce by 150.8 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. Oldenburger-lokalteil.de needs all CSS files to be minified and compressed as it can save up to 150.8 kB or 74% of the original size.
Number of requests can be reduced by 55 (46%)
120
65
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oldenburger Lokalteil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
oldenburger-lokalteil.de
597 ms
www.oldenburger-lokalteil.de
1220 ms
style.css
301 ms
dropdown.css
201 ms
jquery.fancybox.css
205 ms
jquery.fancybox-thumbs.css
203 ms
jquery-ui.css
309 ms
socialshareprivacy-min.css
206 ms
avatars.css
304 ms
imgareaselect.css
304 ms
dashicons.min.css
505 ms
thickbox.css
307 ms
styles.css
398 ms
styles.css
399 ms
polls-css.css
402 ms
awpcpstyle.css
510 ms
jquery.js
716 ms
jquery-migrate.min.js
499 ms
jquery.fancybox.js
699 ms
jquery.easing.js
501 ms
jquery.fancybox-thumbs.js
600 ms
jquery-ui.js
1305 ms
jquery.adrotate.dyngroup.js
603 ms
jquery.adrotate.clicktracker.js
610 ms
tools.js
700 ms
dropdown.js
702 ms
util.js
711 ms
social_bookmarks-min.js
712 ms
jquery.imgareaselect.min.js
714 ms
thickbox.js
716 ms
jquery.form.min.js
727 ms
scripts.js
729 ms
polls-js.js
813 ms
wp-embed.min.js
814 ms
e-201611.js
7 ms
woys3c.css
403 ms
woys3c.js
402 ms
e-201611.js
36 ms
fonts.css
615 ms
wp-emoji-release.min.js
105 ms
search.png
911 ms
logo.png
900 ms
twitter_bw.png
884 ms
facebook_bw.png
885 ms
youtube_bw.png
886 ms
rss_bw.png
883 ms
wetter.com.png
886 ms
wimmeltmp.png
963 ms
timthumb.php
893 ms
comments.png
893 ms
timthumb.php
895 ms
timthumb.php
909 ms
timthumb.php
912 ms
timthumb.php
913 ms
timthumb.php
916 ms
timthumb.php
917 ms
timthumb.php
918 ms
timthumb.php
919 ms
timthumb.php
920 ms
timthumb.php
921 ms
timthumb.php
928 ms
timthumb.php
930 ms
timthumb.php
931 ms
timthumb.php
933 ms
timthumb.php
934 ms
timthumb.php
939 ms
timthumb.php
940 ms
timthumb.php
944 ms
timthumb.php
945 ms
timthumb.php
944 ms
timthumb.php
947 ms
timthumb.php
948 ms
timthumb.php
949 ms
timthumb.php
953 ms
timthumb.php
949 ms
timthumb.php
953 ms
likebox.php
882 ms
ga.js
792 ms
g.gif
786 ms
timthumb.php
185 ms
timthumb.php
183 ms
timthumb.php
180 ms
timthumb.php
180 ms
timthumb.php
179 ms
McLpmVM3wCm.css
192 ms
VH4VPudaxfN.css
186 ms
1kPfZUdGrka.js
199 ms
Yuj_Y8xNH2C.js
221 ms
Mpe38fuBVZ2.js
194 ms
n8qIhCw3vMx.js
195 ms
timthumb.php
172 ms
timthumb.php
342 ms
timthumb.php
340 ms
timthumb.php
334 ms
timthumb.php
324 ms
timthumb.php
322 ms
timthumb.php
321 ms
timthumb.php
397 ms
timthumb.php
402 ms
timthumb.php
407 ms
timthumb.php
398 ms
timthumb.php
405 ms
timthumb.php
394 ms
footer-logo.png
484 ms
s.jpg
483 ms
sb.jpg
486 ms
wpzoom.png
484 ms
Wetterwidget-niedrig.jpg
484 ms
loadingAnimation.gif
480 ms
pontanosans-regular-webfont.woff
568 ms
poly-regular-webfont.woff
556 ms
__utm.gif
38 ms
246635_472798409426965_1204201487_n.jpg
119 ms
542590_371949266178547_466187405_n.jpg
116 ms
11015126_1579794142262522_2953388419137700648_n.jpg
109 ms
1379841_10150004552801901_469209496895221757_n.jpg
107 ms
12274658_878449958917498_5953105900858488643_n.jpg
109 ms
12119168_116808205342176_2667597266417706552_n.jpg
111 ms
942592_106221886419169_4318658818762978670_n.jpg
109 ms
1530475_1718681865066373_5641531565959056276_n.jpg
112 ms
wL6VQj7Ab77.png
82 ms
s7jcwEQH7Sx.png
80 ms
VXcANLwwL5J.js
6 ms
AmlxWlqMvlv.js
6 ms
d_3_M.png
196 ms
oldenburger-lokalteil.de accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
oldenburger-lokalteil.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
oldenburger-lokalteil.de SEO score
N/A
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oldenburger-lokalteil.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Oldenburger-lokalteil.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.
oldenburger-lokalteil.de
Open Graph description is not detected on the main page of Oldenburger Lokalteil. 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: