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.