2.1 sec in total
355 ms
1.1 sec
692 ms
Click here to check amazing Alweg content. Otherwise, check out these important facts you probably never knew about alweg.com
The Alweg Archives website describes and continuously updates the history of the Alweg Monorail Company of Cologne, Germany, and New York and Seattle, USA, and the lasting influence of the Alweg monor...
Visit alweg.comWe analyzed Alweg.com page load time and found that the first response time was 355 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
alweg.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value6.4 s
10/100
25%
Value3.5 s
88/100
10%
Value30 ms
100/100
30%
Value0.01
100/100
15%
Value4.8 s
78/100
10%
355 ms
28 ms
66 ms
46 ms
80 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 41% of them (25 requests) were addressed to the original Alweg.com, 59% (36 requests) were made to Fonts.bunny.net. The less responsive or slowest element that took the longest time to load (355 ms) belongs to the original domain Alweg.com.
Page size can be reduced by 363.6 kB (18%)
2.0 MB
1.6 MB
In fact, the total size of Alweg.com main page is 2.0 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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 41.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. 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 41.9 kB or 78% of the original size.
Potential reduce by 316.7 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. Obviously, Alweg needs image optimization as it can save up to 316.7 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 262 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 4.7 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. Alweg.com needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 15% of the original size.
Number of requests can be reduced by 7 (32%)
22
15
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alweg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for CSS and as a result speed up the page load time.
www.alweg.com
355 ms
style.min.css
28 ms
style.css
66 ms
normalize.css
46 ms
fontawesome-all.min.css
80 ms
unsemantic.css
50 ms
css
32 ms
style.css
51 ms
public.css
52 ms
jquery.min.js
92 ms
jquery-migrate.min.js
72 ms
common.js
76 ms
cropped-company.jpg
34 ms
cropped-Alweg.jpg
79 ms
The-Development-of-the-ALWEG-Monorail-from-the-Beginning-to-the-Present-766x500.jpg
77 ms
monorail-1.png
187 ms
KL-Monorail.jpg
161 ms
tokyo-monorail-1024x576.jpg
63 ms
disney-monorail.jpg
162 ms
Complete-History-of-the-Alweg-Monorail-System.jpg
85 ms
Alweg-2-1.jpg
102 ms
The-Development-of-the-ALWEG-Monorail-from-the-Beginning-to-the-Present-150x150.jpg
104 ms
Complete-History-of-the-Alweg-Monorail-System-150x150.jpg
105 ms
open-sans-cyrillic-ext-400-normal.woff
9 ms
open-sans-vietnamese-400-normal.woff
15 ms
open-sans-latin-ext-400-normal.woff
24 ms
open-sans-greek-ext-400-normal.woff
33 ms
open-sans-cyrillic-400-normal.woff
33 ms
open-sans-hebrew-400-normal.woff
33 ms
open-sans-latin-400-normal.woff
37 ms
open-sans-greek-400-normal.woff
35 ms
open-sans-cyrillic-ext-700-normal.woff
34 ms
open-sans-vietnamese-700-normal.woff
217 ms
open-sans-latin-ext-700-normal.woff
35 ms
open-sans-greek-ext-700-normal.woff
34 ms
open-sans-cyrillic-700-normal.woff
35 ms
open-sans-hebrew-700-normal.woff
37 ms
open-sans-latin-700-normal.woff
36 ms
open-sans-greek-700-normal.woff
37 ms
fa-solid-900.ttf
58 ms
fa-regular-400.ttf
59 ms
fa-brands-400.ttf
58 ms
dosis-vietnamese-700-normal.woff
11 ms
dosis-latin-ext-700-normal.woff
6 ms
dosis-latin-700-normal.woff
7 ms
open-sans-cyrillic-ext-400-italic.woff
9 ms
open-sans-vietnamese-400-italic.woff
8 ms
open-sans-latin-ext-400-italic.woff
9 ms
open-sans-greek-ext-400-italic.woff
17 ms
open-sans-cyrillic-400-italic.woff
17 ms
open-sans-hebrew-400-italic.woff
17 ms
open-sans-latin-400-italic.woff
15 ms
open-sans-greek-400-italic.woff
19 ms
open-sans-cyrillic-ext-700-italic.woff
17 ms
open-sans-vietnamese-700-italic.woff
20 ms
open-sans-latin-ext-700-italic.woff
19 ms
open-sans-greek-ext-700-italic.woff
19 ms
open-sans-cyrillic-700-italic.woff
20 ms
open-sans-hebrew-700-italic.woff
20 ms
open-sans-latin-700-italic.woff
21 ms
open-sans-greek-700-italic.woff
21 ms
alweg.com 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
alweg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
alweg.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alweg.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Alweg.com 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.
alweg.com
Open Graph data is detected on the main page of Alweg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: