From 103421b9f5a1483c301226d9fa60fafe63bca923 Mon Sep 17 00:00:00 2001
From: FurkanK <122597204+FurKay00@users.noreply.github.com>
Date: Tue, 11 Jun 2024 08:27:26 +0200
Subject: [PATCH] Update METRICS_REPORT.md

---
 docs/METRICS_REPORT.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/METRICS_REPORT.md b/docs/METRICS_REPORT.md
index 51b221bd..9b90475b 100644
--- a/docs/METRICS_REPORT.md
+++ b/docs/METRICS_REPORT.md
@@ -7,4 +7,11 @@ In this document, we are reporting the results of the additional metrics we have
   
 ### Web Application Performance
 We have used the web extension 'PageSpeed Insights' to evaluate our website in regards to its rendering and response performance. The following image contains the result for the current state of our application:
+  
 ![grafik](https://github.com/SE-TINF22B6/DHBWhub/assets/122597204/926b8fe6-249c-4f37-8ab8-a33762f730e6)
+
+The high score on best practices is just what we wanted to achieve with our component based architecture on the frontend. The low score on the response time was quite expected, since there are several reasons for it:
+1. On the homepage, all the posts are retrieved from the database every time you enter it or refresh the tab. The reason is to provide consistent data which is conform to the data in the database.
+2. Our backend is located on a BWcloud server which was provided for free for every student in the region. Thus, there are obviously restrictions regarding the request and response times between the backend and the frontend.
+   
+### Web Application Monitoring