3 sec in total
414 ms
2.3 sec
251 ms
Welcome to autopumpkin.de homepage info - get ready to check Auto Pumpkin best content for Germany right away, or after learning these important things about autopumpkin.de
Pumpkin Android Autoradio mit Bluetooth für die meisten Automodelle, unterstützt DAB+ Android Auto WLAN 4G Rückfahrkamera, OBD2, Mirrorlink, Carplay, USB, SD
Visit autopumpkin.deWe analyzed Autopumpkin.de page load time and found that the first response time was 414 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
autopumpkin.de performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value11.8 s
0/100
25%
Value7.4 s
28/100
10%
Value1,270 ms
19/100
30%
Value0
100/100
15%
Value12.7 s
14/100
10%
414 ms
243 ms
242 ms
329 ms
69 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 52% of them (33 requests) were addressed to the original Autopumpkin.de, 14% (9 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Cdn.shopify.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Autopumpkin.de.
Page size can be reduced by 468.6 kB (34%)
1.4 MB
907.0 kB
In fact, the total size of Autopumpkin.de main page is 1.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 449.8 kB which makes up the majority of the site volume.
Potential reduce by 378.1 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 64.2 kB, which is 14% 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 378.1 kB or 84% of the original size.
Potential reduce by 1.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. Auto Pumpkin images are well optimized though.
Potential reduce by 89.3 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 89.3 kB or 20% of the original size.
Potential reduce by 0 B
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. Autopumpkin.de has all CSS files already compressed.
Number of requests can be reduced by 34 (71%)
48
14
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Auto Pumpkin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.autopumpkin.de
414 ms
uc.js
243 ms
pwacompat.min.js
242 ms
webfont.js
329 ms
vendor.min.css
69 ms
theme-styles.scss.css
81 ms
theme-styles-responsive.scss.css
101 ms
jquery.min.js
92 ms
jquery-cookie.min.js
126 ms
lazysizes.min.js
126 ms
preloads.js
327 ms
load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js
325 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
323 ms
js
330 ms
tms-translator.min.js
320 ms
shopify-perf-kit-unstable.min.js
313 ms
vendor.min.js
363 ms
api.jquery.js
314 ms
option_selection-86cdd286ddf3be7e25d68b9fc5965d7798a3ff6228ff79af67b3f4e41d6a34be.js
363 ms
jquery.sticky.js
434 ms
ella.min.js
381 ms
template7.js
362 ms
jquery.tmpl.min.js
313 ms
jquery.products.min.js
363 ms
slick.min.js
434 ms
trekkie.storefront.f9102b76c4156d18a2f9ad80e236ecd6fdcc057c.min.js
319 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
319 ms
shopify-boomerang-1.0.0.min.js
318 ms
sdk.js
242 ms
payment-icon-w.png
248 ms
homepageLOGOblack.png
224 ms
language-white-4d09967be3fd63008e12859a0d408c04.svg
213 ms
8AAngBY2BkYGDgA2IJBhBgAvKZGViBJAuYxwAABJsAOgAAeAFjYGBgZACCk535hiD60tn0azAaAEqpB6wAAA==
10 ms
fontawesome-webfont.woff
141 ms
fontawesome-webfont.woff
256 ms
2-banner-1880x720_4a28c055-facf-41e0-be3a-9e86952f00f2.jpg
142 ms
E6_86f263bc-cc6f-4813-967f-507acd2bd80f_300x.jpg
304 ms
E8_35a4caf8-788f-463a-a5a1-6ce51905c504_300x.jpg
1011 ms
E2_06471c1d-4a6d-4a2b-97eb-dfe70eb14ebd_300x.jpg
1013 ms
E2_90d3b3b1-76c9-4fa0-8bf7-fbcc9898794e_300x.jpg
1013 ms
E22_300x.jpg
1012 ms
css
126 ms
sdk.js
16 ms
769 ms
pxiEyp8kv8JHgFVrJJfedA.woff
58 ms
pxiByp8kv8JHgFVrLGT9Z1xlEw.woff
58 ms
pxiByp8kv8JHgFVrLDz8Z1xlEw.woff
738 ms
pxiByp8kv8JHgFVrLFj_Z1xlEw.woff
741 ms
pxiGyp8kv8JHgFVrLPTucHtG.woff
744 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
745 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
743 ms
pxiByp8kv8JHgFVrLDD4Z1xlEw.woff
743 ms
pxiByp8kv8JHgFVrLBT5Z1xlEw.woff
743 ms
fontawesome-webfont.ttf
741 ms
fontawesome-webfont.ttf
728 ms
loader.js
224 ms
like.php
153 ms
fontawesome-webfont.svg
140 ms
base.css
32 ms
nIvNRKOdND_.js
118 ms
FEppCFCt76d.png
97 ms
conversions.js
91 ms
installed.js
137 ms
tptinstall.min.js
22 ms
autopumpkin.de accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
autopumpkin.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
Browser errors were logged to the console
Page has valid source maps
autopumpkin.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Autopumpkin.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Autopumpkin.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.
autopumpkin.de
Open Graph description is not detected on the main page of Auto Pumpkin. 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: