5.3 sec in total
1.6 sec
3 sec
571 ms
Click here to check amazing GLOSE content for France. Otherwise, check out these important facts you probably never knew about glose.fr
Glose.fr est à la croisée entre le site lifestyle, le guide d'adresses sélectif à Paris & le journal de bord d'une parisienne de 40 ans. Il touche essentiellement les parisien(ne)s, trentena...
Visit glose.frWe analyzed Glose.fr page load time and found that the first response time was 1.6 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
glose.fr performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value26.6 s
0/100
25%
Value13.7 s
2/100
10%
Value8,130 ms
0/100
30%
Value0
100/100
15%
Value27.1 s
0/100
10%
1647 ms
164 ms
171 ms
181 ms
166 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 56% of them (35 requests) were addressed to the original Glose.fr, 18% (11 requests) were made to Youtube.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Glose.fr.
Page size can be reduced by 539.7 kB (71%)
755.4 kB
215.7 kB
In fact, the total size of Glose.fr main page is 755.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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. CSS take 367.0 kB which makes up the majority of the site volume.
Potential reduce by 193.5 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. This page needs HTML code to be minified as it can gain 27.3 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 193.5 kB or 85% of the original size.
Potential reduce by 11.7 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. Obviously, GLOSE needs image optimization as it can save up to 11.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 24.3 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 24.3 kB or 34% of the original size.
Potential reduce by 310.1 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Glose.fr needs all CSS files to be minified and compressed as it can save up to 310.1 kB or 85% of the original size.
Number of requests can be reduced by 35 (80%)
44
9
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GLOSE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
glose.fr
1647 ms
sgr.css
164 ms
style.min.css
171 ms
styles.css
181 ms
wpp.css
166 ms
css
37 ms
main.css
416 ms
font-awesome.4.7.0.swap.min.css
177 ms
weather-icon.swap.css
242 ms
penci-icon.css
245 ms
style.css
253 ms
social-counter.css
258 ms
sgr.js
256 ms
wpp.min.js
324 ms
jquery.min.js
404 ms
jquery-migrate.min.js
339 ms
tsg_new_window.js
341 ms
swfobject.js
346 ms
audio-player-noswfobject.js
405 ms
regenerator-runtime.min.js
385 ms
wp-polyfill.min.js
384 ms
index.js
385 ms
penci-lazy.js
403 ms
libs-script.min.js
624 ms
main.js
416 ms
post-like.js
429 ms
style.css
260 ms
gtm.js
191 ms
loader.js
138 ms
cmp.js
149 ms
european_lifestyle_216px.png
177 ms
deco.png
369 ms
lifestyle_winner.svg
737 ms
84_9umjddI0
257 ms
glose-logo.gif
438 ms
paris.gif
437 ms
carte-paris-petite-arron.gif
437 ms
paris-chic-bobo-insolite.gif
438 ms
mes-adresses2.gif
438 ms
quitter-paris.jpg
438 ms
lieux-recherche.gif
437 ms
fontawesome-webfont.woff
217 ms
penciicon.ttf
217 ms
analytics.js
168 ms
js
167 ms
www-player.css
57 ms
www-embed-player.js
55 ms
base.js
55 ms
fetch-polyfill.js
55 ms
84_9umjddI0
111 ms
www-player.css
81 ms
www-embed-player.js
69 ms
base.js
115 ms
fetch-polyfill.js
68 ms
collect
272 ms
ad_status.js
184 ms
gJfj2lBrymlHLmhPScFZFm4D3a7BBd9OMx4--DsdpK8.js
136 ms
embed.js
46 ms
collect
152 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
119 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
119 ms
id
39 ms
glose.fr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
glose.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
glose.fr 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
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glose.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Glose.fr 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.
glose.fr
Open Graph data is detected on the main page of GLOSE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: