On today’s web, a web page needs to load fast and have a great user experiencein order to be successful. The faster the better. A server side rendered webpage can have a prominent initial load speed while a client side rendered webpage will have a great interactive user experience. When combining the two,some users with a bad internet connection or a slow device could receive a pooruser experience. A new technology called Amplified Mobile Pages (AMP) wascreated by Google to help combat this issue.The authors of this report gives an answer to if Google AMP could maintain theuser experience while still contributing with a fast initial load speed for applica-tions. To do this, we conducted an experiment through creating a Google AMPapplication and compared it to another application using a different renderingengine called Pug. We have also measured the metrics: page load time, speedindex and application size between the two applications. To fully understandthe AMP format, the authors conducted a literature study, to further strengthentheir findings.Google AMP is a great technology but it can still grow to become better. Theformat could increase the speed of a website, however the same result could beachieved without AMP if focus was set on writing a fast application. From theexperiment, the authors concluded that Google AMP takes a great time to learnbecause of its own version of JavaScript through modules. The format also hasa different structure than standard HTML. From the tests, a smaller applica-tion does not favor the implementation of AMP. We did however derive fromthe experiment and the literature study that bigger applications could benefitfrom the perks of AMP and could therefor be a potential choice for old and newapplications.

Progressive Web Applications are becoming more advanced and have increased user activity year after year, especially on mobile platforms. But still the standard of performance does not in most cases meet what we expect in relation to the time it takes to load these. Technologies are evolving as an attempt to change this, and one that has gained a lot of attention in recent years is Google AMP (Accelerated Mobile Pages). A technology that initially aimed at very simple content, but which has recently become more advanced but has its main focus on performance. An entire application does not need to be developed with this technology, but a noted method is to use it as an entry-point to another application as an attempt to reduce the initial load time for the user and enhance the experience in later navigations. This report investigates with an experiment how the AMP technology stands against another technology focused on speed, in this case the JavaScript framework Gatsby. This is done with the frameworks as a combination using AMP as an entry-point and also developed separately, all with enhanced Progressive Web App features. To make development easier and understand the difference of applications included in the study, a literature study was also done with focus on this aspect. At the point when the applications became published and available through Google search and measurements for the applications were made, it was discovered that their metrics load time, start render and speed index all had major performance improvements for the AMP applications on the first load with a mobile device utilizing Google cache CDN, but the effect was not as great on desktop. The implementation process differs some in the frameworks included, and turned out to be more restricted with AMP with the desired effect of increasing performance. While the second framework Gatsby is developed more flexible and could be seen as a more modern way of developing.  It shows a positive opportunity to combine technologies to serve content to a user faster on mobile devices, which could be an action to speed up the web and maintain the user experience.