5.4 sec in total
306 ms
4.6 sec
568 ms
Welcome to royalcig.fr homepage info - get ready to check Royalcig best content right away, or after learning these important things about royalcig.fr
Découvrez notre large sélection de cigarettes électroniques, e-liquides et accessoires pour tous les vapoteurs.
Visit royalcig.frWe analyzed Royalcig.fr page load time and found that the first response time was 306 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
royalcig.fr performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value11.6 s
0/100
25%
Value9.8 s
10/100
10%
Value1,880 ms
9/100
30%
Value0.217
57/100
15%
Value22.3 s
1/100
10%
306 ms
590 ms
298 ms
476 ms
305 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 64% of them (71 requests) were addressed to the original Royalcig.fr, 24% (27 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Royalcig.fr.
Page size can be reduced by 326.4 kB (25%)
1.3 MB
990.5 kB
In fact, the total size of Royalcig.fr main page is 1.3 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. 60% of websites need less resources to load. Images take 491.6 kB which makes up the majority of the site volume.
Potential reduce by 271.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. This page needs HTML code to be minified as it can gain 75.8 kB, which is 25% 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 271.7 kB or 90% of the original size.
Potential reduce by 8.3 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. Royalcig images are well optimized though.
Potential reduce by 38.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 7.5 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. Royalcig.fr has all CSS files already compressed.
Number of requests can be reduced by 62 (82%)
76
14
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royalcig. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
royalcig.fr
306 ms
royalcig.fr
590 ms
fonts.css
298 ms
theme.css
476 ms
paypal_fo.css
305 ms
productcomments.css
307 ms
rs6.css
311 ms
front.css
317 ms
jquery.fancybox.css
559 ms
front.css
558 ms
ph_simpleblog-17.css
561 ms
custom.css
574 ms
front.css
571 ms
frontend.min.css
728 ms
front.css
812 ms
front.css
815 ms
custom_s_1.css
809 ms
front.css
823 ms
front.css
824 ms
custom_s_1.css
981 ms
front.css
1075 ms
custom_s_1.css
1065 ms
iqitmegamenu_s_1.css
1070 ms
custom.css
1081 ms
font-awesome-preload.css
1079 ms
css
41 ms
core.js
1391 ms
theme.js
1540 ms
ps_emailsubscription.js
1310 ms
conversion-api.js
1339 ms
jquery.rating.plugin.js
1339 ms
productListingComments.js
1353 ms
jquery.fitvids.js
1567 ms
function.js
1576 ms
front.js
1574 ms
GoogleAnalyticActionLib.js
1657 ms
jquery.fancybox.js
1661 ms
ps_shoppingcart.js
1764 ms
front.js
1821 ms
ph_simpleblog-17.js
1548 ms
masonry.pkgd.min.js
1550 ms
instagramLite.min.js
1662 ms
jquery-numerator.min.js
1641 ms
lottie-player.js
1735 ms
frontend.js
1632 ms
front.js
1541 ms
front.js
1550 ms
front.js
1654 ms
custom_s_1.js
1651 ms
front.js
1735 ms
custom.js
1619 ms
rbtools.min.js
1651 ms
rs6.min.js
1759 ms
analytics.js
168 ms
lgpng.png
262 ms
logo-1671688928.jpg
1531 ms
royalcig.png
2364 ms
e-liquide-Music-juice.png
1888 ms
Fichier%207v3.svg
1531 ms
Fichier%208v3.svg
1605 ms
Fichier%2010v4.svg
1727 ms
eighteen.png
1828 ms
0711ea4439a6-850x550.jpg
75 ms
36.jpg
1679 ms
69.jpg
1801 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf
72 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf
108 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf
158 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf
158 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf
158 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf
158 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
157 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
179 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
182 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
182 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
182 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
182 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
182 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
182 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
225 ms
pxiGyp8kv8JHgFVrJJLucHtF.ttf
225 ms
pxiDyp8kv8JHgFVrJJLmg1hVF9eL.ttf
225 ms
pxiDyp8kv8JHgFVrJJLm21lVF9eL.ttf
225 ms
pxiDyp8kv8JHgFVrJJLmv1pVF9eL.ttf
225 ms
pxiAyp8kv8JHgFVrJJLmE0tCMPc.ttf
225 ms
pxiDyp8kv8JHgFVrJJLmr19VF9eL.ttf
225 ms
pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf
226 ms
pxiDyp8kv8JHgFVrJJLm111VF9eL.ttf
227 ms
pxiDyp8kv8JHgFVrJJLm81xVF9eL.ttf
225 ms
ke80OhoaMkR6-hSn7kbHVoFf7ZfgMPr_nTorBcwXKw.ttf
227 ms
ke80OhoaMkR6-hSn7kbHVoFf7ZfgMPr_nQIpBcwXKw.ttf
227 ms
ke85OhoaMkR6-hSn7kbHVoFf7ZfgMPr_lbkMFQ.ttf
227 ms
ec.js
51 ms
collect
48 ms
embed
385 ms
Poppins-Regular.woff
1925 ms
fontawesome-webfont.woff
1957 ms
PlayfairDisplay-Regular.woff
1999 ms
js
190 ms
PlayfairDisplaySC-Bold.woff
2023 ms
161.jpg
1883 ms
162.jpg
1948 ms
133.jpg
1931 ms
136.jpg
1979 ms
137.jpg
2024 ms
Copie%20de%20Gold%20Black%20Vintage%20Baroque%20Luxury%20Frame%20Business%20Facebook%20Cover%20(1640%C2%A0%C3%97%C2%A0600%C2%A0px)%20(2).jpg
2000 ms
js
29 ms
geometry.js
4 ms
search.js
8 ms
main.js
13 ms
css
23 ms
royalcig.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.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
royalcig.fr 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
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
royalcig.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 Royalcig.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 Royalcig.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.
royalcig.fr
Open Graph data is detected on the main page of Royalcig. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: