5.7 sec in total
1.2 sec
4.2 sec
273 ms
Welcome to airport-weeze.de homepage info - get ready to check Airport Weeze best content for Germany right away, or after learning these important things about airport-weeze.de
Die offizielle Seite für den Airport Weeze | Alle Infos zu Anfahrt & Parken, Flugplan, Abflug, Ankunft | Ziele, Restaurants & Services.
Visit airport-weeze.deWe analyzed Airport-weeze.de page load time and found that the first response time was 1.2 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
airport-weeze.de performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value13.3 s
0/100
25%
Value11.5 s
5/100
10%
Value1,050 ms
25/100
30%
Value0.226
55/100
15%
Value13.4 s
11/100
10%
1236 ms
848 ms
571 ms
288 ms
18 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 94% of them (62 requests) were addressed to the original Airport-weeze.de, 2% (1 request) were made to Google.com and 2% (1 request) were made to Myvirtualpaper.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Airport-weeze.de.
Page size can be reduced by 361.7 kB (26%)
1.4 MB
1.0 MB
In fact, the total size of Airport-weeze.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. 30% of websites need less resources to load. Images take 949.4 kB which makes up the majority of the site volume.
Potential reduce by 45.9 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 21.5 kB, which is 40% 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 45.9 kB or 85% of the original size.
Potential reduce by 72.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. Airport Weeze images are well optimized though.
Potential reduce by 185.8 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 185.8 kB or 63% of the original size.
Potential reduce by 57.6 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. Airport-weeze.de needs all CSS files to be minified and compressed as it can save up to 57.6 kB or 84% of the original size.
Number of requests can be reduced by 19 (29%)
65
46
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Airport Weeze. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
en
1236 ms
styles.css
848 ms
home.css
571 ms
versie2.css
288 ms
jsapi
18 ms
jquery-ui-1.8.10.custom.min.js
859 ms
formvalidation.js
435 ms
jquery.tooltip.min.js
572 ms
jquery.lightbox-0.5.js
867 ms
cufon-yui-1_09i.js
858 ms
MetaBook-Roman_400.font.js
834 ms
miniflipper.js
18 ms
js.js
721 ms
intro_hype_generated_script.js
298 ms
jquery.min.js
30 ms
print-EN.css
162 ms
header-image-mask-home.png
290 ms
loader.gif
146 ms
logo-airport-weeze.gif
292 ms
bullet-1.png
161 ms
ryanair-banner.gif
294 ms
1-webseiteweeze.gif
422 ms
du.gif
288 ms
nl.gif
307 ms
uk.gif
427 ms
searchbox-left.gif
440 ms
searchbox-right.gif
439 ms
social-sprite-24x24.png
704 ms
bullet-4.png
448 ms
06_airlines&reiseveranstalter-4747-3.jpg
908 ms
02.2_anabreise-4553-3.jpg
1110 ms
06_airlines&reiseveranstalter-pan01.jpg
1481 ms
blockhome-top.png
584 ms
tab-bg.png
599 ms
btn-left.png
721 ms
btn-right.png
740 ms
blockhome-bg.png
840 ms
mainnav-active.gif
862 ms
mainnav-mask.png
884 ms
body-bg-default.png
1703 ms
blocksmall-top.png
1004 ms
tab-bg-right.png
1031 ms
blocksmall-bg.png
1050 ms
home-flights.png
1442 ms
bullet-1b.png
1179 ms
ryanair-logo.png
1197 ms
blocksmall-bg-orange.png
1251 ms
byebye_Banner_2810.gif
1476 ms
675_aw_bannerryanair_en.jpg
1556 ms
block-top-white.png
1404 ms
block-bg.png
1549 ms
analytics.js
36 ms
HYPE.js
1652 ms
jquery.form.js
1487 ms
120x600_en.png
1678 ms
footer-bg.gif
1410 ms
bullet-5.png
1420 ms
fuss1.gif
145 ms
fuss2.gif
144 ms
fuss3.gif
142 ms
fuss4.gif
145 ms
403_BigBanner_AWC_Bike.png
143 ms
over_bike.gif
236 ms
403_BigBanner_AWC_Banner.png
281 ms
403_BigBanner_AWC_URL.png
283 ms
403_BigBanner_AWC_anmelden.png
281 ms
airport-weeze.de accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
airport-weeze.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
airport-weeze.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
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 Airport-weeze.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 Airport-weeze.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.
airport-weeze.de
Open Graph description is not detected on the main page of Airport Weeze. 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: