7.4 sec in total
1.5 sec
5.3 sec
595 ms
Click here to check amazing Prudential Com content for Cambodia. Otherwise, check out these important facts you probably never knew about prudential.com.kh
នៅពេលមានករណីជំងឺមហារីក ឬជំងឺធ្ងន់ធ្ងរ ៤៩ ករណីផ្សេងទៀត ដែលស្ថិតក្រោមលក្ខខណ្ឌការពាររបស់យើងបានកើតឡើង នោះយើងនឹងជួយអ្នកក្នុងការគ្រប់គ្រងលើការចំណាយ
Visit prudential.com.khWe analyzed Prudential.com.kh page load time and found that the first response time was 1.5 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
prudential.com.kh performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value10.5 s
0/100
25%
Value17.9 s
0/100
10%
Value15,410 ms
0/100
30%
Value0.113
86/100
15%
Value20.6 s
2/100
10%
1506 ms
398 ms
523 ms
57 ms
72 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that 40% of them (10 requests) were addressed to the original Prudential.com.kh, 36% (9 requests) were made to Fonts.gstatic.com and 12% (3 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 Prudential.com.kh.
Page size can be reduced by 59.0 kB (29%)
204.3 kB
145.2 kB
In fact, the total size of Prudential.com.kh main page is 204.3 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. 45% of websites need less resources to load. Javascripts take 73.1 kB which makes up the majority of the site volume.
Potential reduce by 59.0 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 8.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 59.0 kB or 85% of the original size.
Potential reduce by 71 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 0 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. Prudential.com.kh has all CSS files already compressed.
Number of requests can be reduced by 7 (54%)
13
6
The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prudential Com. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
www.prudential.com.kh
1506 ms
398 ms
styles.min.css
523 ms
css
57 ms
notosanskhmer.css
72 ms
utilsGA.min.js
1004 ms
jquery.min.js
1550 ms
scripts.min.js
1585 ms
_Incapsula_Resource
48 ms
gtm.js
296 ms
spinner.gif
710 ms
ijw3s5roRME5LLRxjsRb-gssOenAyendxrgV2c-Zw-9vbVUti_Z_dWgtWYuNAKz_mgI.ttf
327 ms
ijw3s5roRME5LLRxjsRb-gssOenAyendxrgV2c-Zw-9vbVUti_Z_dWgtWYu_AKz_mgI.ttf
329 ms
ijw3s5roRME5LLRxjsRb-gssOenAyendxrgV2c-Zw-9vbVUti_Z_dWgtWYvTAKz_mgI.ttf
924 ms
ijw3s5roRME5LLRxjsRb-gssOenAyendxrgV2c-Zw-9vbVUti_Z_dWgtWYsNAKz_mgI.ttf
357 ms
ijw3s5roRME5LLRxjsRb-gssOenAyendxrgV2c-Zw-9vbVUti_Z_dWgtWYuNAaz_mgI.ttf
528 ms
ijw3s5roRME5LLRxjsRb-gssOenAyendxrgV2c-Zw-9vbVUti_Z_dWgtWYtTB6z_mgI.ttf
518 ms
ijw3s5roRME5LLRxjsRb-gssOenAyendxrgV2c-Zw-9vbVUti_Z_dWgtWYtqB6z_mgI.ttf
908 ms
ijw3s5roRME5LLRxjsRb-gssOenAyendxrgV2c-Zw-9vbVUti_Z_dWgtWYsNB6z_mgI.ttf
905 ms
ijw3s5roRME5LLRxjsRb-gssOenAyendxrgV2c-Zw-9vbVUti_Z_dWgtWYskB6z_mgI.ttf
884 ms
icomoon.ttf
882 ms
analytics.js
652 ms
gtm.js
239 ms
js
620 ms
arrow-right.svg
396 ms
prudential.com.kh accessibility score
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
Buttons do not have an accessible 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.
prudential.com.kh best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
prudential.com.kh 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
KM
KM
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prudential.com.kh can be misinterpreted by Google and other search engines. Our service has detected that Cambodian is used on the page, and it matches the claimed language. Our system also found out that Prudential.com.kh 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.
prudential.com.kh
Open Graph data is detected on the main page of Prudential Com. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: