2.8 sec in total
318 ms
1.5 sec
908 ms
Click here to check amazing Mobile Geev content for France. Otherwise, check out these important facts you probably never knew about mobile.geev.com
Geev is the first place to donate food and objects and allows individuals to donate free of charge to other people in his area. In a single gesture, collect furniture or bicycles for free. Let's give ...
Visit mobile.geev.comWe analyzed Mobile.geev.com page load time and found that the first response time was 318 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
mobile.geev.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value7.7 s
3/100
25%
Value4.6 s
70/100
10%
Value2,010 ms
7/100
30%
Value0.378
28/100
15%
Value12.4 s
15/100
10%
318 ms
1047 ms
65 ms
46 ms
58 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Mobile.geev.com, 72% (42 requests) were made to Static.geev.com and 14% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Mobile.geev.com.
Page size can be reduced by 1.0 MB (18%)
5.7 MB
4.6 MB
In fact, the total size of Mobile.geev.com main page is 5.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 986.1 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 986.1 kB or 73% of the original size.
Potential reduce by 49.5 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. Mobile Geev images are well optimized though.
Number of requests can be reduced by 9 (19%)
48
39
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Geev. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
mobile.geev.com
318 ms
en
1047 ms
client
65 ms
css2
46 ms
css2
58 ms
css2
64 ms
gtm.js
46 ms
logo_geev_white_en.svg
67 ms
btn_help_center.svg
44 ms
dropdown_close.svg
459 ms
background_hero.svg
46 ms
btn_download_apple_en.svg
449 ms
btn_download_android_en.svg
61 ms
img_app_preview_en.png
58 ms
Picture_1.png
58 ms
Picture_2.png
59 ms
Picture_3.png
65 ms
Picture_4.png
110 ms
Picture_5.png
68 ms
Picture_6.png
108 ms
Picture_7.png
109 ms
Picture_8.png
111 ms
Picture_9.png
115 ms
Picture_10.png
110 ms
Picture_11.png
111 ms
Picture_12.png
112 ms
Picture_13.png
117 ms
Picture_14.png
117 ms
Picture_15.png
124 ms
Picture_16.png
142 ms
Picture_17.png
123 ms
Picture_18.png
122 ms
h2_line_1.svg
141 ms
h2_line_2.svg
142 ms
action_1_en.png
158 ms
action_2_en.png
158 ms
action_3_en.png
158 ms
tf1.png
164 ms
france2.png
210 ms
france3.png
208 ms
france5.png
209 ms
m6.png
211 ms
title_categories_decoration.svg
210 ms
logo_geev_yellow_en.svg
171 ms
logo_instagram.svg
162 ms
logo_linkedIn.svg
172 ms
logo_twitter.svg
168 ms
logo_facebook.svg
171 ms
logo_tiktok.svg
171 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
19 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf
36 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
51 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
50 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
52 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
51 ms
t5t7IRoeKYORG0WNMgnC3seB1YXqips.ttf
109 ms
t5tmIRoeKYORG0WNMgnC3seB7Tk.ttf
107 ms
styles.aed25c13aa882fe1.css
14 ms
mobile.geev.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
mobile.geev.com 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
Missing source maps for large first-party JavaScript
mobile.geev.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Mobile.geev.com 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 Mobile.geev.com 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.
mobile.geev.com
Open Graph data is detected on the main page of Mobile Geev. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: