Leading Edge Web Solutions for Leading Edge Visions
Online marketing services and web infrastructures with a positive impact
We only accept positive, sustainable and organic projects
Enterprise Security for every project
The security of our clients and partners is extremely important to us.
We care about your success and goals
Your success is our success. We value long term partnerships.
Maintenance and updates
Systems are always monitored, upgraded and patched with the latest updates.
Are you looking for a trustworthy partner to bring your vision out into this online world?
ALLUMWANDLUNG approaches your vision in a holistic way, bringing together leading edge know-how in web services, custom programming, online marketing services as well as design and branding, to create a WIN-WIN-WIN for everyone.
For us a web project is more than a virtual business card – it is an opportunity to positively influence life on this planet. We are excited to bring your vision into reality.
– Bernard Bury, Director
Our Services
Cloud Solution (CDN)
Your project will run on the data center network that consists of 180+ PoPs World wide, it has a track record of mitigating the largest DDOS attacks ever recorded.
Processor Power
Our unmetered CPU policy means you don’t have to worry about CPU and cores. We do not hold back any resources for your project.
Cyber Security
Our platform is designed with a very high level of security, with all servers being secured by AppArmor and other security measures.
Backups
We run two backups per day: Day-time backups which are kept for 3 days and nightly backups which are kept for 30 days. Backups can be restored in minutes.
Time is money – How much is 1 second worth to you?
Science shows that a one second delay, makes conversions drop by 7% – 10%
If your site makes $ 1000 per day, a 1 second improvement in page speed brings $70 – $100 extra, every day.
Speed impacts search ranking, mobile visitor happiness, conversion, page views, visit length, bounce rate and many more things…
The example of a single page load
1. User clicks on a link
The user clicks on a link, and the browser checks the IP of the domain in DNS, and then sends the request for the page to the server. If the link uses SSL, the client and server negotiate a secure link before the request is completed.
2. Server makes the page
The server receives the request, and runs the code of your website. The website queries the database and file system for all the required bits and pieces and compiles the HTML page.
3. HTML is sent to the browser
When the HTML is made, the server sends it back to the browser over the internet.
4. The browser requests assets
The browser receives the HTML, reads the code, and figures out it needs many more assets. The assets can come from the same server, or other servers that require new DNS lookups and SSL connections.
5. The browser renders the page
While still collecting the assets, the browser starts putting together html, stylesheets, fonts, images and scripts piece by piece.
6. Display a first version
When the browser has received and put together the part of the page that will be visible, it makes the first contentful paint and displays it. Because the page is not finished loading, the user can not interact with the page yet.
7. Make it ready for interaction
More of the page needs to be put together before the user can start interacting, clicking or scrolling.
8. Page is ready to use
When all assets have completed loading, and all scripts have completed their setup tasks, the page is finally ready to use.
So what does this mean in the context of web performance?
Server response time
The response time of HTML, or the time to first byte, is what has the single largest impact on the user experience. If this first request is slow, all other steps in viewing the web page will be delayed.
There are two options for challenging the response time. You can either make the server do the same amount of work faster, or you can reduce the amount of work that needs to be done.
The workload can be reduced by reducing the complexity, make fewer database requests, and increase the quality of code. Server speed can be increased by changing to faster hosting, or by optimizing the existing hosting stack. Adding more servers will not make it faster.
Network transfer time
The time it takes to transport something from A to B depends on two things. The amount of data and the distance it needs to travel.
Think of internet packages as a DHL delivery lorry. If the packages are more than what can fit in the lorry, it has to ride another round trip for the remaining packages.
Packages will arrive fast if delivery is just down the road, and delivery will be even faster if everything can be transported in one go. Transport will take much longer if the delivery is in a neighbouring city, and even longer if it has to ride multiple times.
So to speed up a web page, you need to make sure to make as few packages as possible, and make sure that the distance from the average website visitor to the server is as short as possible.
Browser render time
The time it takes to render a page is defined by the quality and complexity of the code that needs to be interpreted, the amount of elements and their size, and the speed of the device that runs the browser.
The speed of devices vary a lot, and is not something we can change. To make render time faster, the workload must be reduced for the browser. The less work the browser has to do, the faster it will render.
A webpage becomes fast when the HTML, CSS and scripts are bug, error and warning free. Error free code will also render nicer, and more consistently across different devices.
To further reduce the workload, unused assets should be removed, and the size of others must be reduced.
Technology we use
