6.7 sec in total
285 ms
4.8 sec
1.6 sec
Visit jollia.com now to see the best up-to-date Jollia content and also check out these interesting facts you probably never knew about jollia.com
Jollia sélectionne, au fil des saisons, des créateurs de bijoux fantaisie tendances et intemporels pour accessoiriser votre look. Expédition 24H, satisfait ou remboursé.
Visit jollia.comWe analyzed Jollia.com page load time and found that the first response time was 285 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
jollia.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value14.0 s
0/100
25%
Value7.6 s
26/100
10%
Value1,430 ms
15/100
30%
Value0.453
20/100
15%
Value16.7 s
5/100
10%
285 ms
36 ms
166 ms
97 ms
317 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Jollia.com, 8% (4 requests) were made to Fonts.googleapis.com and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Jollia.fr.
Page size can be reduced by 120.0 kB (12%)
1.0 MB
902.3 kB
In fact, the total size of Jollia.com main page is 1.0 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. 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. Images take 551.5 kB which makes up the majority of the site volume.
Potential reduce by 119.7 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 119.7 kB or 81% of the original size.
Potential reduce by 0 B
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. Jollia images are well optimized though.
Potential reduce by 222 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 103 B
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. Jollia.com has all CSS files already compressed.
Number of requests can be reduced by 25 (58%)
43
18
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jollia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.jollia.fr
285 ms
8236f978f391a776c77c9c7c075388b8.min.css
36 ms
2c05cf5d83b92659afeacb57bbcf676d.min.css
166 ms
styles-l.min.css
97 ms
css2
317 ms
css2
328 ms
logo.svg
132 ms
aurelie-joliff-bijoux.jpg
969 ms
agnes-paris_1.jpg
969 ms
slider-la2l_1.jpg
869 ms
perles-fines_3.jpg
860 ms
email-decode.min.js
330 ms
8c0b59d3d2952e439e29ffa003ee8d87.min.js
569 ms
2315f3aa0317b65f9ee0567d3.js
739 ms
tp.widget.bootstrap.min.js
849 ms
v652eace1692a40cfa3763df669d7439c1639079717194
830 ms
cite.png
513 ms
css2
408 ms
pxiEyp8kv8JHgFVrFJDUdVNF.ttf
908 ms
pxiByp8kv8JHgFVrLEj6V1tvEv-L.ttf
1223 ms
pxiByp8kv8JHgFVrLCz7V1tvEv-L.ttf
1232 ms
icomoon.svg
1086 ms
icomoon.woff
1083 ms
E21i_d3kivvAkxhLEVZpcy96COKv.ttf
1458 ms
gtm.js
865 ms
tp.min.js
864 ms
fbevents.js
1006 ms
css2
101 ms
js-translation.json
828 ms
es6-collections.min.js
746 ms
FormData.min.js
574 ms
load
685 ms
ajax-loader.gif
351 ms
index
678 ms
h.png
1593 ms
1583617551654593
147 ms
analytics.js
137 ms
conversion_async.js
395 ms
leadtag.js
379 ms
core.js
502 ms
loader.js
349 ms
optimize.js
391 ms
collect
81 ms
collect
203 ms
220 ms
main.8f82d377.js
69 ms
ga-audiences
41 ms
16 ms
sb-tracker.js
596 ms
print.min.css
15 ms
jollia.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
jollia.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
jollia.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
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 Jollia.com 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 Jollia.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.
jollia.com
Open Graph description is not detected on the main page of Jollia. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: