508 ms in total
27 ms
355 ms
126 ms
Click here to check amazing Personaldna content for United States. Otherwise, check out these important facts you probably never knew about personaldna.com
PersonalityDNA is a scientific, free, fast, accurate personality test. Learn what makes your personality unique.
Visit personaldna.comWe analyzed Personaldna.com page load time and found that the first response time was 27 ms and then it took 481 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.
personaldna.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value20.0 s
0/100
25%
Value6.4 s
40/100
10%
Value1,030 ms
26/100
30%
Value0.368
29/100
15%
Value9.7 s
28/100
10%
27 ms
10 ms
16 ms
13 ms
14 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 97% of them (77 requests) were addressed to the original Personaldna.com, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to 24.media.tumblr.com. The less responsive or slowest element that took the longest time to load (222 ms) relates to the external source 24.media.tumblr.com.
Page size can be reduced by 1.1 MB (78%)
1.4 MB
299.7 kB
In fact, the total size of Personaldna.com main page is 1.4 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. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 6.1 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 6.1 kB or 78% of the original size.
Potential reduce by 1.7 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. Personaldna images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 79% of the original size.
Number of requests can be reduced by 69 (91%)
76
7
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Personaldna. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
personaldna.com
27 ms
font-awesome.css
10 ms
bootstrap.min.css
16 ms
angular-snap-only.min.css
13 ms
app.css
14 ms
jquery.min.js
15 ms
angular.min.js
25 ms
angular-ui-router.min.js
23 ms
famous-global.js
30 ms
famous-angular.js
25 ms
ngStorage.min.js
23 ms
underscore-min.js
25 ms
moment.min.js
27 ms
TweenMax.min.js
28 ms
TimelineLite.min.js
31 ms
Draggable.min.js
34 ms
ThrowPropsPlugin.min.js
33 ms
CSSPlugin.min.js
37 ms
angular-scroll.min.js
35 ms
angular-snap.min.js
37 ms
snap.min.js
38 ms
index.js
42 ms
nav.js
43 ms
footer.js
44 ms
config.js
46 ms
login-controller.js
46 ms
thanks-controller.js
46 ms
reset-controller.js
55 ms
menu-controller.js
56 ms
assessment-start-controller.js
57 ms
assessment-end-controller.js
57 ms
questions-controller.js
58 ms
sliders-controller.js
59 ms
grid-controller.js
66 ms
bucket-controller.js
67 ms
boolean-controller.js
68 ms
connector-controller.js
66 ms
mc-controller.js
66 ms
free-input-controller.js
66 ms
assessment.css
71 ms
daily.css
64 ms
fonts.css
63 ms
index.css
65 ms
login.css
65 ms
menu.css
65 ms
nav.css
70 ms
questions.css
71 ms
report.css
70 ms
reset.css
71 ms
shared.css
70 ms
thanks.css
68 ms
invite.css
73 ms
admin.css
74 ms
bank-controller.js
72 ms
personality-report-controller.js
159 ms
daily-controller.js
158 ms
invite-controller.js
159 ms
admin-controller.js
154 ms
helpers-factory.js
154 ms
login-factory.js
153 ms
color-factory.js
151 ms
notification-factory.js
152 ms
oauth-factory.js
151 ms
questions-factory.js
144 ms
assessment-factory.js
144 ms
report-factory.js
144 ms
dailyDNA-factory.js
143 ms
dates-factory.js
142 ms
status-factory.js
142 ms
social-factory.js
136 ms
admin-factory.js
135 ms
css
23 ms
tumblr_mvqiyv9aqK1r94argo1_500.png
222 ms
login.html
9 ms
pdna_logo.png
18 ms
Facebook.png
5 ms
Twitter.png
7 ms
lato-v11-latin-700.woff
7 ms
lato-v11-latin-regular.woff
8 ms
personaldna.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.
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.
personaldna.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
personaldna.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Personaldna.com 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 Personaldna.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.
personaldna.com
Open Graph description is not detected on the main page of Personaldna. 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: