18.8 sec in total
3.1 sec
15.1 sec
607 ms
Click here to check amazing Portador content. Otherwise, check out these important facts you probably never knew about portador.de
Visit portador.deWe analyzed Portador.de page load time and found that the first response time was 3.1 sec and then it took 15.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
portador.de performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value8.2 s
2/100
25%
Value6.0 s
46/100
10%
Value850 ms
34/100
30%
Value0.06
98/100
15%
Value8.5 s
38/100
10%
3087 ms
307 ms
26 ms
724 ms
620 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 63% of them (67 requests) were addressed to the original Portador.de, 15% (16 requests) were made to Gravatar.com and 4% (4 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (9.6 sec) belongs to the original domain Portador.de.
Page size can be reduced by 840.9 kB (31%)
2.7 MB
1.9 MB
In fact, the total size of Portador.de main page is 2.7 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 63.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. 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 63.8 kB or 81% of the original size.
Potential reduce by 146.2 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. Portador images are well optimized though.
Potential reduce by 355.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 355.4 kB or 58% of the original size.
Potential reduce by 275.4 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. Portador.de needs all CSS files to be minified and compressed as it can save up to 275.4 kB or 78% of the original size.
Number of requests can be reduced by 55 (53%)
103
48
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portador. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
portador.de
3087 ms
gtranslate-style16.css
307 ms
css
26 ms
dashicons.min.css
724 ms
admin-bar.min.css
620 ms
style.css
317 ms
bbpress.css
1155 ms
buddymenu-style.css
331 ms
admin-bar.min.css
488 ms
styles.css
515 ms
style.min.css
648 ms
adminbar.min.css
662 ms
foundation-nonresponsive.min.css
963 ms
font-awesome.min.css
752 ms
prettyPhoto.css
955 ms
mediaelementplayer.min.css
961 ms
default.css
1088 ms
style.css
970 ms
responsive.css
1129 ms
css
14 ms
css
22 ms
jquery.js
3182 ms
jquery-migrate.min.js
1108 ms
widget-groups.min.js
1120 ms
swtcptcf.js
1232 ms
confirm.min.js
1252 ms
script.min.js
1264 ms
global.js
1432 ms
comment-reply.min.js
1294 ms
element.js
32 ms
admin-bar.min.js
832 ms
231992
72 ms
jquery.form.min.js
851 ms
scripts.js
865 ms
foundation.min.js
1885 ms
jquery.inview.min.js
968 ms
jquery.carouFredSel-6.2.0-packed.js
969 ms
jquery.mousewheel.min.js
854 ms
jquery.touchSwipe.min.js
2411 ms
jquery.transit.min.js
992 ms
jquery.ba-throttle-debounce.min.js
997 ms
jquery.knob.js
1108 ms
jquery.quovolver.js
1132 ms
jquery.backgroundSize.js
1131 ms
jquery.prettyPhoto.js
1404 ms
retina.js
1263 ms
mediaelement-and-player.min.js
1563 ms
app.js
1391 ms
widgets.js
6 ms
app.css
1549 ms
logo.png
755 ms
b858eabd492ab806ac3a42b4c79d227c
60 ms
main-bg11.png
156 ms
black_pattern.gif
305 ms
header41.png
715 ms
small_logo.png
366 ms
gray_pattern.gif
302 ms
023182295f4a20a215793336601a678c-bpfull.png
9628 ms
2d74c83a118fde8f7c577b2c62271772-bpfull.png
1116 ms
82ddb43e0741bdef6b74b9a43ff38426-bpfull.jpg
1668 ms
blank.png
392 ms
dtc-pictures.png
1442 ms
dtc-tattooshops.png
2793 ms
dtc-groups.png
1267 ms
status_01.png
1278 ms
status_02.png
1421 ms
status_03.png
1419 ms
status_04.png
1560 ms
2d2c8891aff1d1e1a762daaced465912-bpfull.png
3154 ms
322f61208c4dbdb524bf52169ca44548-bpfull.jpg
1729 ms
d0bc4645e6ee04356e53c5d2381c6226-bpfull.jpg
2664 ms
3495f6a7d5fa8146afb9531bacf67eeb
114 ms
f00f17e8d7b50841be47f7144c560e64
117 ms
94f7ac8d15918908b122ad39f2d20ae5
117 ms
f0f8936ad6dc3e974656600e18ac16cb
117 ms
b81a6b47a323f49b9ff097dadfe10e14
118 ms
f5c484500d286856fcf2d45c253c5a5a
125 ms
c2652e95d6fa044040525a314d5d4fb3
128 ms
26c035679a880b5d2d4313716e29f6c9
140 ms
b858eabd492ab806ac3a42b4c79d227c
140 ms
3495f6a7d5fa8146afb9531bacf67eeb
139 ms
f00f17e8d7b50841be47f7144c560e64
145 ms
94f7ac8d15918908b122ad39f2d20ae5
149 ms
f0f8936ad6dc3e974656600e18ac16cb
149 ms
b81a6b47a323f49b9ff097dadfe10e14
296 ms
f5c484500d286856fcf2d45c253c5a5a
296 ms
16.png
1956 ms
fontawesome-webfont.woff
1996 ms
translateelement.css
49 ms
main.js
89 ms
gray_pattern.gif
45 ms
map-bg.png
41 ms
up_page.png
2028 ms
sclytics.js
23 ms
banners
179 ms
element_main.js
172 ms
231992
22 ms
analytics.js
149 ms
loading_dark.gif
1868 ms
uaxZ57m0Wee5vur9ZBrzicxk+132zMsNMs5i12ZitKcc9L43z7nlxz4t7Xtzz4p4X97y456WV474X9720+Q9k+OnYAAABUrRnegAA
57 ms
collect
45 ms
translate_24dp.png
60 ms
l
53 ms
rhpop_1.1.42.js
55 ms
collect
26 ms
collect
79 ms
portador.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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
portador.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
portador.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 uses legible font sizes
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portador.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 Portador.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.
portador.de
Open Graph description is not detected on the main page of Portador. 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: