5.9 sec in total
333 ms
5 sec
532 ms
Click here to check amazing A1 content for Austria. Otherwise, check out these important facts you probably never knew about a1.net
Alles aus einer Hand. Internet, TV, Mobil- & Festnetztelefonie, unbegrenztes Festnetz-Internet für zuhause und kostenloses WLAN-Modem.
Visit a1.netWe analyzed A1.net page load time and found that the first response time was 333 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
a1.net performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value24.7 s
0/100
25%
Value17.8 s
0/100
10%
Value8,470 ms
0/100
30%
Value0.01
100/100
15%
Value31.7 s
0/100
10%
333 ms
345 ms
1129 ms
547 ms
327 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 23% of them (17 requests) were addressed to the original A1.net, 19% (14 requests) were made to Cdn11.a1.net and 19% (14 requests) were made to Cdn13.a1.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Cdn11.a1.net.
Page size can be reduced by 570.0 kB (23%)
2.4 MB
1.9 MB
In fact, the total size of A1.net main page is 2.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. 35% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 88.6 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 24.3 kB, which is 23% 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 88.6 kB or 85% of the original size.
Potential reduce by 159.1 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. A1 images are well optimized though.
Potential reduce by 322.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 322.3 kB or 73% of the original size.
Number of requests can be reduced by 22 (33%)
66
44
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
a1.net
333 ms
www.a1.net
345 ms
www.a1.net
1129 ms
combined.css
547 ms
combined.js
327 ms
combined.js
325 ms
combined.js
961 ms
combined.js
504 ms
combined.js
502 ms
combined.js
502 ms
logo.jpg
1199 ms
Promo-Flappe-A1-One-200x178.jpg
1201 ms
icons-sc-chat-40x40.png
696 ms
icons-sc-kontakt-40x40.png
1209 ms
icons-sc-telefon-40x40.png
1208 ms
icons-sc-community-40x40.png
1207 ms
icons-sc-a1-shops-40x40.png
1202 ms
icon-adv-Weniger-Kosten-60x60.png
1201 ms
icon-adv-a1-60x60.png
1428 ms
ht-TopAngebote-640x229.jpg
1644 ms
qt-res-a1-blog-generic-290x135.jpg
1535 ms
qt-res-onlinevorteile-startseite-generic-290x135.jpg
1643 ms
social3.png
1547 ms
icons-sc-fb-40x40.png
1207 ms
sf-A1One-1920x1080.jpg
1550 ms
sf-Neuheiten-Bestseller-1920x1080.jpg
1648 ms
icon-adv-startseite-quicklinks-webmail-60x60.png
1206 ms
icon-adv-stern-60x60.png
1207 ms
ht-big-Go-Tarif-ohne-Handy-611x218.jpg
2406 ms
ht-res-sgs6-generic-610x218.jpg
2406 ms
qt-res-kombinierensparen-startseite-generic-290x135.jpg
1546 ms
social1.png
1535 ms
social4.png
2512 ms
icon-social-a1-blog-39x39.jpg
2548 ms
icons-sc-a1-guru-40x40.png
1205 ms
sf-netcube-1920x1080.jpg
1646 ms
sf-fni-pur-v2-1920x1080.jpg
2439 ms
sf-GalaxyS7-Pre-Order-1920x1080.jpg
1612 ms
rht-neuheiten-bestseller-generic-04-290x268.jpg
1205 ms
icon-adv-speedtest-60x60.png
1423 ms
icon-adv-Tarif-Angebot-60x60.png
1534 ms
ht-Xcite-640x229.jpg
2403 ms
qt-mein-A1-290x135.jpg
2437 ms
social2.png
2545 ms
blank.gif
336 ms
a1_iconfont.woff
492 ms
a1_regular.woff
1051 ms
a1_medium.woff
1051 ms
gtm.js
490 ms
gtm.js
515 ms
info-a1net-neu
602 ms
sf-Smartphone-Neuheiten-TEST-160x75.jpg
1353 ms
sf-A1One-160x75.jpg
1349 ms
sf-netcube-160x75.jpg
1352 ms
sf-GalaxyS7-Pre-Order-160x75.jpg
1457 ms
fbevents.js
287 ms
oct.js
33 ms
analytics.js
29 ms
iframe_api
53 ms
adsct
112 ms
adsct
108 ms
ec.js
31 ms
collect
88 ms
collect
40 ms
www-widgetapi.js
75 ms
collect
42 ms
collect
12 ms
collect
35 ms
ga-audiences
50 ms
ga-audiences
47 ms
33 ms
A1-Homepage-InfoLayer-Bild-W1024.jpg
567 ms
overlaybackground.png
264 ms
combined.css
319 ms
a1.net 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 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.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
a1.net 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
a1.net 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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A1.net can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that A1.net 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.
a1.net
Open Graph description is not detected on the main page of A1. 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: