3.3 sec in total
26 ms
2.8 sec
470 ms
Click here to check amazing Edit DNS content. Otherwise, check out these important facts you probably never knew about editdns.net
DNS servers handle billions of requests every day; ensure the best performance of your internet infrastructure through Dyn's Managed DNS services - the most resilient DNS management network in the wor...
Visit editdns.netWe analyzed Editdns.net page load time and found that the first response time was 26 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
editdns.net performance score
26 ms
20 ms
40 ms
25 ms
19 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Editdns.net, 25% (33 requests) were made to Dyn.com and 8% (10 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (736 ms) relates to the external source App-sj08.marketo.com.
Page size can be reduced by 1.5 MB (71%)
2.1 MB
623.6 kB
In fact, the total size of Editdns.net main page is 2.1 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. 75% 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. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 83.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 83.1 kB or 76% of the original size.
Potential reduce by 3.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. Edit DNS images are well optimized though.
Potential reduce by 1.1 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.1 MB or 71% of the original size.
Potential reduce by 273.7 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. Editdns.net needs all CSS files to be minified and compressed as it can save up to 273.7 kB or 88% of the original size.
Number of requests can be reduced by 76 (84%)
91
15
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edit DNS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
editdns.net
26 ms
20 ms
2573310155.js
40 ms
dyn-uikit.css
25 ms
style.css
19 ms
forms2.js
34 ms
jquery.js
224 ms
uikit.js
236 ms
jquery-migrate-1.2.1.js
20 ms
scroll.js
19 ms
dynevents.min.js
30 ms
ip.json
362 ms
event
345 ms
geo2.js
295 ms
event
437 ms
evergage.min.js
435 ms
6W7BE-M5LXH-CTY93-2NS7S-Z92YG
293 ms
MasterTMS.min.js
343 ms
getForm
736 ms
retina-dyn-sprite.png
205 ms
ip4d.jpg
202 ms
exp-latency.jpg
192 ms
WB061_Homepage.jpg
202 ms
FreeExpressCampaignBG.jpg
201 ms
main-02.min.js
118 ms
site-scripts.js
125 ms
jquery.maskedinput.min.js
167 ms
international-phone-mask.js
169 ms
latest-referrer.js
168 ms
gtm.js
265 ms
AvenirLTW04_35Light.woff
110 ms
AvenirLTW04_95Black.woff
110 ms
SourceSansPro-Light.woff
203 ms
SourceSansPro-ExtraLight.woff
200 ms
SourceSansPro-Regular.woff
304 ms
SourceSansPro-Semibold.woff
200 ms
SourceSansPro-Bold.woff
199 ms
SourceSansPro-Black.woff
200 ms
fontawesome-webfont.woff
204 ms
SourceSansPro-LightIt.woff
202 ms
SourceSansPro-ExtraLightIt.woff
199 ms
SourceSansPro-It.woff
200 ms
SourceSansPro-SemiboldIt.woff
203 ms
SourceSansPro-BoldIt.woff
206 ms
SourceSansPro-BlackIt.woff
205 ms
event
109 ms
tags
114 ms
conversion_async.js
204 ms
roundtrip.js
202 ms
analytics.js
203 ms
munchkin.js
195 ms
plusone.js
361 ms
dyn.beacon.min.js
191 ms
bizible.js
376 ms
tag.js
347 ms
code.js
377 ms
4yYUFLVN.min.js
184 ms
spx
344 ms
twreceiver
212 ms
forms2.css
115 ms
forms2-theme-simple.css
118 ms
275 ms
munchkin.js
102 ms
collect
207 ms
ip.json
209 ms
pixel
200 ms
cb=gapi.loaded_0
294 ms
cb=gapi.loaded_1
344 ms
fastbutton
339 ms
yieldify_1457450204.js
127 ms
visitWebPage
409 ms
capture-apps-3.0.2.js
254 ms
collect
321 ms
pixel
98 ms
GHFR32IHVFFQ7NLB7K7VTM.js
401 ms
305 ms
spx
270 ms
spx
276 ms
st
281 ms
collect
114 ms
XDFrame
508 ms
cb=gapi.loaded_0
120 ms
cb=gapi.loaded_1
112 ms
postmessageRelay
118 ms
st
76 ms
gs
232 ms
ga-audiences
24 ms
3193398744-postmessagerelay.js
67 ms
rpc:shindig_random.js
34 ms
fbevents.hashing.js
128 ms
out
29 ms
30 ms
47 ms
40 ms
45 ms
62 ms
out
22 ms
out
22 ms
out
24 ms
out
25 ms
out
28 ms
out
26 ms
out
27 ms
out
28 ms
cb=gapi.loaded_0
52 ms
64 ms
u.php
126 ms
sync
40 ms
adsct
146 ms
pixel
104 ms
81 ms
74 ms
74 ms
56 ms
377928.gif
37 ms
sd
33 ms
st
116 ms
st
140 ms
133 ms
tap.php
18 ms
in
6 ms
forms2.min.js
27 ms
generic
13 ms
generic
8 ms
ipv
52 ms
504175.js
15 ms
genieTracker.php
205 ms
BizibleAcct.js
76 ms
kvp
33 ms
genieTracker.php
408 ms
editdns.net SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Editdns.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Editdns.net 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.
editdns.net
Open Graph description is not detected on the main page of Edit DNS. 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: