13.2 sec in total
560 ms
11.4 sec
1.2 sec
Click here to check amazing Cantika content for Indonesia. Otherwise, check out these important facts you probably never knew about cantika.com
Inspirasi seputar lifestyle bagi wanita, kecantikan, fashion, cinta, kesehatan, karir, keluarga, zodiak, hingga kuliner - Cantika.com
Visit cantika.comWe analyzed Cantika.com page load time and found that the first response time was 560 ms and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cantika.com performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value8.4 s
2/100
25%
Value17.1 s
0/100
10%
Value3,810 ms
1/100
30%
Value0.846
4/100
15%
Value17.1 s
4/100
10%
560 ms
1310 ms
302 ms
225 ms
640 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 7% of them (10 requests) were addressed to the original Cantika.com, 27% (38 requests) were made to Statik.tempo.co and 13% (18 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source Statik.tempo.co.
Page size can be reduced by 302.3 kB (23%)
1.3 MB
1.0 MB
In fact, the total size of Cantika.com 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. 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 746.4 kB which makes up the majority of the site volume.
Potential reduce by 229.2 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 229.2 kB or 87% of the original size.
Potential reduce by 72.4 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. Cantika images are well optimized though.
Potential reduce by 630 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 29 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. Cantika.com has all CSS files already compressed.
Number of requests can be reduced by 59 (46%)
129
70
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cantika. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
cantika.com
560 ms
www.cantika.com
1310 ms
ats.js
302 ms
6c5466dd765a76945ca168198afeab096270f511.js
225 ms
style.css
640 ms
css
446 ms
191906-32373363052129.js
448 ms
gpt.js
223 ms
core.js
1178 ms
main.js
1178 ms
rfp-infeed.js
442 ms
izooto.js
144 ms
pubads_impl_2022092001.js
231 ms
ppub_config
687 ms
rid
590 ms
analytics.js
921 ms
atrk.js
744 ms
plugin.min.js
920 ms
1144066_400.jpg
1771 ms
logo-1-white.png
881 ms
cantik-logo.png
1484 ms
1138167_400.jpg
1805 ms
1144165_400.jpg
1166 ms
1132115_400.jpg
1661 ms
1143811_400.jpg
2211 ms
1133272_400.jpg
2219 ms
913663_400.jpg
2220 ms
1144109_400.jpg
2698 ms
1120786_400.jpg
2588 ms
1143820_400.jpg
2563 ms
1141813_400.jpg
4057 ms
1143888_720.jpg
4055 ms
1143823_720.jpg
4053 ms
1143681_720.jpg
4053 ms
1143456_720.jpg
4056 ms
1144135_400.jpg
4054 ms
1070129_400.jpg
4254 ms
1143644_400.jpg
4252 ms
1141671_400.jpg
5049 ms
1138074_400.jpg
4606 ms
1131001_400.jpg
4252 ms
1144097_400.jpg
4253 ms
1015684_400.jpg
4629 ms
1110037_400.jpg
4629 ms
1143823_400.jpg
5048 ms
983159_400.jpg
5047 ms
910628_400.jpg
5252 ms
1143791_400.jpg
5687 ms
1127721_400.jpg
4735 ms
1138909_400.jpg
6297 ms
1130022_400.jpg
5251 ms
1104496_400.jpg
5251 ms
868433_400.jpg
5251 ms
1143816_400.jpg
6444 ms
1143925_400.jpg
6448 ms
1091434_400.jpg
6295 ms
cygnus
722 ms
hb.emxdgt.com
772 ms
cantika.ttf
612 ms
play.png
524 ms
atrk.gif
217 ms
collect
59 ms
collect
126 ms
ga-audiences
37 ms
1093580_400.jpg
5151 ms
integrator.js
208 ms
ads
734 ms
container.html
37 ms
1143874_400.jpg
4665 ms
16977441884885307578
425 ms
icon.png
428 ms
abg_lite.js
536 ms
window_focus.js
569 ms
rx_lidar.js
585 ms
ext.js
483 ms
adsbygoogle.js
1859 ms
j01nivdj.js
2325 ms
integrator.js
272 ms
ads
1630 ms
ads
1391 ms
container.html
1491 ms
ptag.js
175 ms
jquery.min.js
140 ms
show_ads_impl.js
112 ms
zrt_lookup.html
464 ms
sodar
306 ms
activeview
110 ms
sodar2.js
69 ms
activeview
62 ms
activeview
62 ms
cookie.js
236 ms
integrator.js
218 ms
ads
364 ms
sodar
194 ms
activeview
276 ms
ads
901 ms
activeview
217 ms
activeview
246 ms
ads
1295 ms
runner.html
95 ms
aframe
111 ms
85254efcadaacab5fed344cbf203b7e7.js
52 ms
load_preloaded_resource.js
40 ms
c471d9b7113df21a6cf58632ab968748.js
73 ms
qs_click_protection.js
40 ms
042791247ab671b2831aa311d6583330.js
434 ms
bD2V1yF27SqeqYvgyYYSPdiNu290SHC9vzB8BmtCvBI.js
407 ms
icon.png
386 ms
s
314 ms
cookie_push_onload.html
314 ms
css
691 ms
dpixel
837 ms
downsize_200k_v1
806 ms
activeview
180 ms
dpixel
464 ms
dpixel
1670 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
2083 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
2126 ms
activeview
811 ms
activeview
1374 ms
pixel
1681 ms
pixel
1137 ms
pixel
474 ms
pixel
376 ms
pixel
376 ms
pixel
362 ms
pixel
359 ms
pixel
241 ms
pixel
139 ms
pixel
158 ms
pixel
144 ms
pixel
145 ms
pixel
132 ms
pixel
129 ms
sodar
121 ms
pixel
119 ms
pixel
121 ms
pixel
112 ms
pixel
102 ms
cantika.com 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
[id] attributes on active, focusable elements are not unique
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
Form elements do not have associated labels
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
cantika.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cantika.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ID
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cantika.com can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it does not match the claimed English language. Our system also found out that Cantika.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.
cantika.com
Open Graph data is detected on the main page of Cantika. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: