5.6 sec in total
336 ms
3.7 sec
1.6 sec
Click here to check amazing One content. Otherwise, check out these important facts you probably never knew about one.at
Alles aus einer Hand. Internet, TV, Mobil- & Festnetztelefonie, unbegrenztes Festnetz-Internet für zuhause und kostenloses WLAN-Modem.
Visit one.atWe analyzed One.at page load time and found that the first response time was 336 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
one.at performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value21.2 s
0/100
25%
Value24.6 s
0/100
10%
Value37,220 ms
0/100
30%
Value0.01
100/100
15%
Value55.6 s
0/100
10%
336 ms
616 ms
464 ms
35 ms
950 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original One.at, 48% (38 requests) were made to Cdn11.a1.net and 22% (17 requests) were made to Cdn13.a1.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Cdn12.a1.net.
Page size can be reduced by 317.9 kB (13%)
2.5 MB
2.2 MB
In fact, the total size of One.at main page is 2.5 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 185.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 185.9 kB or 85% of the original size.
Potential reduce by 127.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. One images are well optimized though.
Potential reduce by 3.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 839 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. One.at has all CSS files already compressed.
Number of requests can be reduced by 15 (21%)
72
57
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of One. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
one.at
336 ms
www.a1.net
616 ms
all_tracking-head.js
464 ms
otSDKStub.js
35 ms
all_css.css
950 ms
all_head.js
489 ms
adrum-config.js
465 ms
adrum.js
647 ms
all_modernizr.js
466 ms
xcite-slider.js
814 ms
jquery.min.js
39 ms
teaser-personalization.js
448 ms
all_base.js
1019 ms
tweetylogin.js
622 ms
all_start.js
461 ms
all_tracking.js
481 ms
flappe-SIMply-A1-Maerz2022-200x178.png
129 ms
promoflappe-bbi-100-euro-aktion-Jul2022-netcube-neukunden-stoerer-200x178.jpg
131 ms
flappe-canal-plus-atl-jun2022-200x178.jpg
562 ms
meineangebote-flappenteaser-bild-generic-res.jpg
562 ms
res-kontaktflappe-contacticon.png
697 ms
sf-bbi-100-euro-aktion-Aug2022-Internet-768x1080.jpg
1787 ms
sf-mobil-SIMply-A1-Maerz2022-768x1080.png
696 ms
sf-mobil-Samsung-Galaxy-Fold4-Flip4-768x1080-2-.jpg
904 ms
bt-a1-jetzt-du-co2-neutral-wave-solo-699x394.jpg
831 ms
social2.jpg
698 ms
icon-social-a1-blog-39x39.jpg
830 ms
logo.jpg
127 ms
icons-sc-community-40x40.png
124 ms
icons-sc-a1-shops-40x40.png
125 ms
icons-sc-a1-guru-40x40.png
126 ms
icons-sc-feedback-40x40.png
130 ms
sf-mobil-iPhone-14-pro-Keyvisual-768x1080.jpg
557 ms
sf-xplore-tv-stream-768x1080.jpg
827 ms
res-rht-2-meine-angebote-745x287.jpg
557 ms
social1.jpg
557 ms
linked-in.png
558 ms
pf-stoerungs-assistent-allgemein-200x178.jpg
102 ms
icons-sc-guded-contact-40x40.png
126 ms
icon-sc-live-shop-red-40x40.png
127 ms
icon_mail_56x56.png
558 ms
icon_rechnung_56x56.png
555 ms
icon_auftragsstatus_56x56.png
555 ms
icon_speedtest_56x56.png
558 ms
icon_stoerungs-assistent_56x56.png
688 ms
icon_a1_56x56.png
690 ms
seniorenhandy-ht-generic-res.jpg
687 ms
ht-iPhone-14-Keyvisual-640x229.jpg
687 ms
social3.jpg
692 ms
Icon-Instagram-40x40.jpg
685 ms
blank.gif
761 ms
A1Sans-Regular.woff
812 ms
A1Sans-Bold.woff
813 ms
a1_iconfont.woff
733 ms
A1Serif-Regular.woff
970 ms
A1Serif-Bold.woff
809 ms
shop-device_iphone-14-pro-deeppurple_313x374.png
862 ms
ndm-Samsung-Galaxy-S22-5G_313x374_222x265.png
696 ms
shop-device_iphone-14-blue_313x374.png
770 ms
shop-dev-galaxy-a53_313_374_222_265.png
695 ms
shop-device_iphone-14-pro-max-deeppurple_313x374.png
847 ms
shop-dev-Galaxy-A33_313x374.png
823 ms
shop-dev_xiaomi12_313_374_313_374.png
874 ms
iphone13-pro-graphite_313_374_313_374.png
1066 ms
shop-dev_iphone-se_313x374_313_374.png
873 ms
shop-dev_FP4_313x374.png
877 ms
nokia-x10-5g-forestgreen_313_374_313_374.png
1257 ms
shop-dev-galaxy-s22-ultra-black_313_374_313_374.png
1157 ms
iphone13-blue_313_374_313_374.png
1072 ms
zte-axon-30-ultra-5g-black_313_374_313_374.png
1074 ms
Vivo-Y52-5G-Black_313_374.png
977 ms
huawei-nova9-black_313_374_313_374.png
1178 ms
7be88f69-ce3a-4f37-9745-bcccebca4374.json
81 ms
otBannerSdk.js
12 ms
de.json
21 ms
otCenterRounded.json
23 ms
otPcCenter.json
34 ms
otCommonStyles.css
34 ms
all_css_print.css
142 ms
one.at 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.
[aria-*] attributes do not have valid values
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
one.at 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
Missing source maps for large first-party JavaScript
one.at 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 One.at 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 One.at 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.
one.at
Open Graph description is not detected on the main page of One. 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: