9.2 sec in total
2.1 sec
6.5 sec
707 ms
Visit janesce.co.nz now to see the best up-to-date Janesce content and also check out these interesting facts you probably never knew about janesce.co.nz
At Janesce NZ, we believe your skin is a reflection of your life. We treat the skin topically with powerful botanicals and from within with skin nutrition.
Visit janesce.co.nzWe analyzed Janesce.co.nz page load time and found that the first response time was 2.1 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
janesce.co.nz performance score
name
value
score
weighting
Value16.6 s
0/100
10%
Value26.0 s
0/100
25%
Value20.3 s
0/100
10%
Value700 ms
42/100
30%
Value0.002
100/100
15%
Value25.3 s
0/100
10%
2081 ms
60 ms
855 ms
642 ms
1070 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 74% of them (78 requests) were addressed to the original Janesce.co.nz, 22% (23 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Janesce.co.nz.
Page size can be reduced by 2.0 MB (50%)
3.9 MB
1.9 MB
In fact, the total size of Janesce.co.nz main page is 3.9 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. 70% of websites need less resources to load. CSS take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 140.6 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 140.6 kB or 81% of the original size.
Potential reduce by 9.6 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. Janesce images are well optimized though.
Potential reduce by 482.2 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 482.2 kB or 71% of the original size.
Potential reduce by 1.3 MB
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. Janesce.co.nz needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 85% of the original size.
Number of requests can be reduced by 68 (89%)
76
8
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Janesce. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
janesce.co.nz
2081 ms
js
60 ms
wp-emoji-release.min.js
855 ms
swiper.min.css
642 ms
style.css
1070 ms
buttons.min.css
644 ms
dashicons.min.css
1067 ms
mediaelementplayer-legacy.min.css
833 ms
wp-mediaelement.min.css
856 ms
media-views.min.css
1286 ms
style.min.css
1048 ms
style.min.css
1492 ms
style.min.css
1070 ms
style.min.css
1263 ms
style.min.css
1282 ms
style.css
1284 ms
styles.css
1286 ms
emily-grace-elements.css
1478 ms
video-container.min.css
1498 ms
style.css
1709 ms
style.css
1496 ms
responsive.css
1496 ms
font-awesome.min.css
1693 ms
responsive.css
1705 ms
css
30 ms
widget.css
1713 ms
elementor-icons.min.css
1712 ms
frontend.min.css
2140 ms
swiper.min.css
1907 ms
post-24325.css
1919 ms
frontend.min.css
2352 ms
global.css
1924 ms
post-308.css
2137 ms
css
31 ms
fontawesome.min.css
2121 ms
solid.min.css
2133 ms
brands.min.css
2144 ms
frontend-gtag.min.js
2336 ms
jquery.min.js
2349 ms
animations.min.css
1769 ms
jquery-migrate.min.js
1743 ms
emily-grace-elements.js
1744 ms
login-with-ajax.legacy.min.js
1725 ms
ajaxify.min.js
1718 ms
imagesloaded.min.js
1734 ms
masonry.min.js
1574 ms
swiper.min.js
1930 ms
index.js
1558 ms
index.js
1702 ms
dlm-xhr.min.js
1525 ms
bxslider.js
1503 ms
slicknav.js
1503 ms
fitvids.js
1501 ms
sticky.js
1700 ms
emgrace.js
1526 ms
comment-reply.min.js
1511 ms
jquery.smartmenus.min.js
1508 ms
webpack-pro.runtime.min.js
1506 ms
webpack.runtime.min.js
1705 ms
frontend-modules.min.js
1514 ms
regenerator-runtime.min.js
1507 ms
wp-polyfill.min.js
1504 ms
hooks.min.js
1508 ms
i18n.min.js
1500 ms
frontend.min.js
1508 ms
waypoints.min.js
1504 ms
core.min.js
1504 ms
frontend.min.js
1303 ms
elements-handlers.min.js
1294 ms
jquery.sticky.min.js
1292 ms
fbevents.js
62 ms
10--scaled.jpg
1261 ms
janesce-logo-black-2.png
1054 ms
80-copy.jpg
1065 ms
2--600x900.jpg
1487 ms
CYMK-BB-Hollie-125-copy-900x900.jpg
1063 ms
MG_5503-copy-847x900.jpg
1279 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mQ.ttf
45 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-PgFoq92mQ.ttf
54 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-BQCoq92mQ.ttf
212 ms
0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0Coq92mQ.ttf
53 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf
54 ms
0QI6MX1D_JOuGQbT0gvTJPa787wsuxJBkqg.ttf
54 ms
0QI6MX1D_JOuGQbT0gvTJPa787zAvBJBkqg.ttf
55 ms
0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqg.ttf
55 ms
S6uyw4BMUTPHjx4wWw.ttf
55 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
56 ms
S6u8w4BMUTPHh30AXC-v.ttf
56 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
57 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
78 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
78 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
79 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
79 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
78 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
80 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
81 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
80 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
81 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
81 ms
fa-brands-400.woff
1228 ms
fa-brands-400.woff
1253 ms
fa-solid-900.woff
1244 ms
fa-solid-900.woff
1435 ms
fa-regular-400.woff
1444 ms
janesce.co.nz 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.
janesce.co.nz 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
Page has valid source maps
janesce.co.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Janesce.co.nz 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 Janesce.co.nz 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.
janesce.co.nz
Open Graph data is detected on the main page of Janesce. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: