3.6 sec in total
341 ms
2.3 sec
950 ms
Click here to check amazing Eff Arr content. Otherwise, check out these important facts you probably never knew about eff-arr.de
This website is for sale! eff-arr.de is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, eff-arr.de has it a...
Visit eff-arr.deWe analyzed Eff-arr.de page load time and found that the first response time was 341 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
eff-arr.de performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value0.9 s
100/100
25%
Value3.0 s
94/100
10%
Value1,140 ms
22/100
30%
Value0.208
60/100
15%
Value3.9 s
89/100
10%
341 ms
156 ms
140 ms
104 ms
34 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Eff-arr.de, 20% (18 requests) were made to Sme-cdn.com and 19% (17 requests) were made to Fabianroemer.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Graph.facebook.com.
Page size can be reduced by 768.6 kB (27%)
2.9 MB
2.1 MB
In fact, the total size of Eff-arr.de main page is 2.9 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 50.8 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 19.6 kB, which is 34% 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 50.8 kB or 89% of the original size.
Potential reduce by 143.3 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. Eff Arr images are well optimized though.
Potential reduce by 238.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 238.4 kB or 64% of the original size.
Potential reduce by 336.0 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. Eff-arr.de needs all CSS files to be minified and compressed as it can save up to 336.0 kB or 83% of the original size.
Number of requests can be reduced by 38 (44%)
87
49
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eff Arr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
eff-arr.de
341 ms
www.fabianroemer.com
156 ms
bootstrap-and-theme.min.css
140 ms
sme.template.css
104 ms
sme.fbfeed.css
34 ms
swally.css
28 ms
main-style.css
34 ms
css
25 ms
jquery.min.js
32 ms
bootstrap.min.js
134 ms
modernizr.min.js
103 ms
uiCore.js
99 ms
ui.mobileCheck.min.js
103 ms
jquery.socl.js
111 ms
fastclick.js
104 ms
jquery.fbfeed.js
105 ms
angular.min.js
49 ms
angular-sanitize.min.js
47 ms
angular-animate.min.js
49 ms
jquery.timeago.js
125 ms
masonry.pkgd.min.js
204 ms
angular-masonry.min.js
127 ms
imagesloaded.pkgd.min.js
209 ms
jquery.swally.min.js
210 ms
jquery.smooth-scroll.min.js
212 ms
jquery.slimscroll.min.js
206 ms
script.js
29 ms
sWallyController.min.js
212 ms
sme.analytics.js
35 ms
retina.min.js
205 ms
bg.jpg
159 ms
ga.js
110 ms
192 ms
recent
821 ms
611084463985004544
156 ms
effarr
189 ms
posts
695 ms
tr
57 ms
logo.jpg
81 ms
logo-mobile.jpg
81 ms
fb.png
80 ms
tw.png
85 ms
ig.png
80 ms
yt.png
87 ms
sp.png
106 ms
fabianroemer_kalenderblaetter_album_cover.jpg
197 ms
fabianroemer_album_cover.jpg
115 ms
bg_1024-768.jpg
119 ms
effarr
307 ms
posts
1242 ms
__utm.gif
30 ms
__utm.gif
17 ms
__utm.gif
17 ms
xNuU0dyr_pE
50 ms
zyLaDQ8oPzo
71 ms
2ILiW127g_0
70 ms
cBp0_RNObeQ
67 ms
njvNqd9NVyg
55 ms
xPF9Q3QTBgQ
79 ms
CWqXvu-xe6Y
83 ms
www-embed-player-vflfNyN_r.css
74 ms
www-embed-lightweight.js
114 ms
proxy.jpg
43 ms
2764.png
40 ms
hqdefault.jpg
175 ms
hqdefault.jpg
130 ms
hqdefault.jpg
99 ms
hqdefault.jpg
106 ms
hqdefault.jpg
105 ms
hqdefault.jpg
150 ms
hqdefault.jpg
132 ms
sddefault.jpg
108 ms
fb.png
156 ms
12821385_961399423913854_7325058511262196030_n.jpg
50 ms
11188876_958280470892416_1114018103_n.jpg
52 ms
12108956_890263447694119_6104681381922889508_n.jpg
22 ms
12688372_944280658959064_2609614928253639364_n.jpg
17 ms
picture-placeholder.png
116 ms
video-preview.png
691 ms
1b351f.dyn
203 ms
12797688_1694557527482565_1919854121_n.jpg
170 ms
opentag-77345-1696599.js
25 ms
partner
360 ms
12328454_683993481740920_1587222259_n.jpg
151 ms
11378018_565233133650829_853272208_n.jpg
148 ms
12825725_1684323845177214_1336298603_n.jpg
157 ms
ig.png
51 ms
tag2
155 ms
pixel
25 ms
pixel
17 ms
eff-arr.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eff-arr.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
eff-arr.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
Document doesn't use legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eff-arr.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 Eff-arr.de 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.
eff-arr.de
Open Graph data is detected on the main page of Eff Arr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: