3.1 sec in total
229 ms
2.3 sec
556 ms
Click here to check amazing Status 1 And content. Otherwise, check out these important facts you probably never knew about status-1and1.mx
IONOS, your digital partner for cloud solutions and web hosting, supporting your needs from websites, domains, servers, and more.
Visit status-1and1.mxWe analyzed Status-1and1.mx page load time and found that the first response time was 229 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
status-1and1.mx performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value5.3 s
22/100
25%
Value4.4 s
75/100
10%
Value9,470 ms
0/100
30%
Value0.038
100/100
15%
Value33.9 s
0/100
10%
229 ms
103 ms
222 ms
225 ms
168 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Status-1and1.mx, 47% (41 requests) were made to Cs.uicdn.net and 1% (1 request) were made to Cu1.uicdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cs.uicdn.net.
Page size can be reduced by 324.6 kB (17%)
1.9 MB
1.6 MB
In fact, the total size of Status-1and1.mx main page is 1.9 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 308.8 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 308.8 kB or 88% of the original size.
Potential reduce by 1.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. Status 1 And images are well optimized though.
Potential reduce by 234 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 14.4 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. Status-1and1.mx needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 21% of the original size.
Number of requests can be reduced by 42 (49%)
86
44
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Status 1 And. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
www.ionos.com
229 ms
fonts.css
103 ms
ionos-us.min.css
222 ms
at.min.js
225 ms
index.css
168 ms
polyfills-c67a75d1b6f99dc8.js
304 ms
sessions.js
113 ms
datalayer.min.js
483 ms
6650.bf895e3bf7753ebc.js
136 ms
6372.4f1ca06e76c1f577.js
318 ms
491.48c908f4237a5b32.js
319 ms
8361.97517671015d0da7.js
320 ms
7131.478435d9efb28be2.js
349 ms
1739.5f5cb97912a81a9e.js
345 ms
6766.9f249b5486863da5.js
356 ms
4238.738afbce5a3d6f63.js
409 ms
7056.21c93093bfdbe1f1.js
409 ms
3610.7d503270778758a3.js
447 ms
webpack-44b20669b438c0d6.js
457 ms
framework-8c779d08cd12e703.js
525 ms
main-04f464d3b74960f6.js
544 ms
_app-e217fd4d4720232b.js
536 ms
9353-04968e711f879836.js
576 ms
1411-ee5962474f4f04e6.js
666 ms
1563-db007428c06de0b4.js
607 ms
701-3d0fd57a8a813f79.js
668 ms
%5B%5B...slug%5D%5D-a1cab0d29777fbb1.js
659 ms
_buildManifest.js
687 ms
_ssgManifest.js
709 ms
48gpcp.js
647 ms
icon-green-electricity.svg
473 ms
ionos.b2910554.svg
453 ms
phone.e4f11652.svg
482 ms
ic-s24-regular-user.900316e1.svg
521 ms
stroke-1.7514e48d.svg
535 ms
ic-s24-regular-arrow-right-white.0a282ab1.svg
557 ms
ic-s24-regular-magnifier_amber.10c39550.svg
587 ms
checkmark.42bdf62f.svg
617 ms
ic-s24-regular-arrow-right-blue.6bc984e7.svg
648 ms
ic-s24-bullet-checkmark.78f25b8f.svg
679 ms
ic-s24-regular-arrow-right-light-blue.60fa826e.svg
708 ms
energy-green.7018e78d.svg
702 ms
instagram.e5fcda11.svg
737 ms
facebook.7f7ee447.svg
752 ms
youtube.aef95fd8.svg
785 ms
vi_psa-nlement_CA.png
474 ms
36382-com-domain-logo-white.svg
470 ms
Brand_Home_Stage_WordPress_US.png
643 ms
icon-product-email.svg
501 ms
icon-product-mywebsite.svg
512 ms
icon-product-webhosting.svg
539 ms
icon-product-deploy-now.svg
597 ms
icon-product-server-virtual-pro.svg
605 ms
icon-product-cloud-compute-engine.svg
620 ms
35197-developer-code-for-ionos.png
816 ms
35041-sysadmin-code-for-ionos-us.png
866 ms
35171-software-engineer-code-for-ionos-us.png
895 ms
35077-design-agency-code-for-ionos.jpg
932 ms
icon-product-cloud-server.svg
727 ms
icon-product-server-dedicated-pro.svg
749 ms
icon-product-wordpress-hosting-managed.svg
854 ms
icon-product-cloud-backup.svg
862 ms
34946-vi-about-facelift.jpg
1334 ms
34947-x-ic-domains.svg
990 ms
34949-around-the-world.svg
998 ms
34634-dedicated-server-pro.svg
975 ms
34948-employees.svg
1011 ms
Home-feature-UK-TVC-PSA-Visuals-Home_mobile.png
1271 ms
34951-contact-person.svg
1081 ms
34953-always-available.svg
1096 ms
34952-certificate.svg
1105 ms
34699-Cloud-Cubes.jpg
1270 ms
34698-Dedi-Server.jpg
1334 ms
icon-product-cloud-managed-database-services.svg
1204 ms
icon-product-cloud-managed-kubernetes.svg
1233 ms
icon-product-cloud-compute-engine.svg
1311 ms
icon-product-cloud-s3-object-storage.svg
1339 ms
34692-domain-generic.svg
1385 ms
34685-webhosting.svg
1393 ms
34631-email-icon-pos.svg
1421 ms
in-linked.8f1c545c.svg
788 ms
tiktok.34c2f3ac.svg
786 ms
34694-sql-server-hosting.svg
1023 ms
34687-mywebsite.svg
973 ms
34684-product-wordpress-hosting.svg
994 ms
34696-ssl-certificate.svg
1011 ms
34664-online-shop.svg
1007 ms
status-1and1.mx 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
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
status-1and1.mx 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
status-1and1.mx 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
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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Status-1and1.mx 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 Status-1and1.mx 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.
status-1and1.mx
Open Graph data is detected on the main page of Status 1 And. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: