5 sec in total
651 ms
4 sec
285 ms
Click here to check amazing Classic Efa content for Germany. Otherwise, check out these important facts you probably never knew about classic.efa.de
Ihr Mobilitätsportal für Reisen mit Bus und Bahn und dem gesamten öffentlichen Personennahverkehr in Deutschland
Visit classic.efa.deWe analyzed Classic.efa.de page load time and found that the first response time was 651 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
classic.efa.de performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value10.4 s
0/100
25%
Value10.2 s
8/100
10%
Value1,780 ms
10/100
30%
Value0
100/100
15%
Value15.2 s
7/100
10%
651 ms
202 ms
200 ms
307 ms
198 ms
Our browser made a total of 27 requests to load all elements on the main page. We found that 85% of them (23 requests) were addressed to the original Classic.efa.de, 11% (3 requests) were made to 0 and 4% (1 request) were made to Efa.de. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Classic.efa.de.
Page size can be reduced by 107.9 kB (32%)
341.1 kB
233.1 kB
In fact, the total size of Classic.efa.de main page is 341.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 216.2 kB which makes up the majority of the site volume.
Potential reduce by 1.7 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 1.7 kB or 45% of the original size.
Potential reduce by 21.4 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. Classic Efa images are well optimized though.
Potential reduce by 77.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 77.3 kB or 69% of the original size.
Potential reduce by 7.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. Classic.efa.de needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 79% of the original size.
Number of requests can be reduced by 3 (12%)
26
23
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Classic Efa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
classic.efa.de
651 ms
navigation.jsp
202 ms
head.jsp
200 ms
start.jsp
307 ms
style_new.css
198 ms
header002.jpg
298 ms
efa_logo.gif
200 ms
flagge_de_de.gif
199 ms
flagge_en_de.gif
200 ms
cookietest.js
202 ms
menu.js
596 ms
kalender.js
388 ms
jquery-1.5.1.min.js
406 ms
anfordern_button.css
199 ms
menu_farbverlauf.gif
197 ms
RequestForm
605 ms
efaportal_highlight.gif
104 ms
efaportal_normal.gif
197 ms
app_gvh_3-1-5.jpg
303 ms
qrcodeapp_2.png
303 ms
mapclient3.png
2460 ms
uhr.jpg
299 ms
DELFI_Logo.jpg
401 ms
connect01_80x60.gif
390 ms
region-hannover.gif
602 ms
fadein.jpg
193 ms
close.gif
203 ms
classic.efa.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
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
classic.efa.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
Issues were logged in the Issues panel in Chrome Devtools
classic.efa.de SEO score
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
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classic.efa.de can be misinterpreted by Google and other search engines. Our service has detected that German 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 Classic.efa.de main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
classic.efa.de
Open Graph description is not detected on the main page of Classic Efa. 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: