3.7 sec in total
423 ms
2.7 sec
572 ms
Visit dpht.co.uk now to see the best up-to-date Dpht content and also check out these interesting facts you probably never knew about dpht.co.uk
Welcome to the Dartmoor Pony Heritage Trust - helping support and preserve the future of the Dartmoor Pony.
Visit dpht.co.ukWe analyzed Dpht.co.uk page load time and found that the first response time was 423 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 60% of websites can load faster.
dpht.co.uk performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value11.7 s
0/100
25%
Value8.0 s
22/100
10%
Value650 ms
46/100
30%
Value0.498
16/100
15%
Value13.4 s
11/100
10%
423 ms
136 ms
87 ms
165 ms
231 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 83% of them (97 requests) were addressed to the original Dpht.co.uk, 5% (6 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (770 ms) belongs to the original domain Dpht.co.uk.
Page size can be reduced by 170.3 kB (8%)
2.0 MB
1.9 MB
In fact, the total size of Dpht.co.uk main page is 2.0 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. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 125.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 125.6 kB or 84% of the original size.
Potential reduce by 31.8 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. Dpht images are well optimized though.
Potential reduce by 1.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 11.2 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. Dpht.co.uk has all CSS files already compressed.
Number of requests can be reduced by 94 (93%)
101
7
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dpht. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 50 to 1 for CSS and as a result speed up the page load time.
dpht.co.uk
423 ms
cuq4wnt.css
136 ms
base.css
87 ms
variation_1.css
165 ms
pmpro-add-paypal-express.css
231 ms
pmpro-advanced-levels.css
244 ms
pmpromc.css
249 ms
rs6.css
252 ms
woocommerce-layout.css
249 ms
woocommerce.css
256 ms
font-awesome.min.css
307 ms
simple-line-icons.css
320 ms
htflexboxgrid.css
318 ms
slick.css
330 ms
woolentor-widgets.css
331 ms
photoswipe.min.css
343 ms
default-skin.min.css
376 ms
frontend.css
394 ms
normalize.css
394 ms
style.css
405 ms
frontend.min.css
411 ms
widget-image.min.css
415 ms
widget-icon-list.min.css
463 ms
widget-social-icons.min.css
478 ms
apple-webkit.min.css
478 ms
shapes.min.css
486 ms
widget-heading.min.css
506 ms
widget-text-editor.min.css
511 ms
elementor-icons.min.css
527 ms
swiper.min.css
544 ms
e-swiper.min.css
548 ms
post-12.css
554 ms
frontend.min.css
575 ms
nicons.css
582 ms
frontend.min.css
679 ms
widget-testimonial.min.css
615 ms
post-8928.css
618 ms
css
62 ms
js
82 ms
install-popup-button.js
105 ms
player.js
110 ms
TweenMax.min.js
62 ms
post-76.css
615 ms
post-336.css
591 ms
p.css
49 ms
frontend.min.css
523 ms
prettyphoto.min.css
506 ms
fontawesome.min.css
494 ms
solid.min.css
496 ms
brands.min.css
507 ms
wc-blocks.css
517 ms
widget-nav-menu.min.css
512 ms
widget-forms.min.css
484 ms
flatpickr.min.css
479 ms
conditionizr-4.3.0.min.js
490 ms
modernizr-2.7.1.min.js
504 ms
jquery.min.js
556 ms
jquery-migrate.min.js
555 ms
scripts.js
539 ms
cookies.js
525 ms
rbtools.min.js
654 ms
rs6.min.js
591 ms
jquery.blockUI.min.js
508 ms
add-to-cart.min.js
517 ms
js.cookie.min.js
477 ms
woocommerce.min.js
471 ms
underscore.min.js
516 ms
wp-util.min.js
528 ms
photoswipe.min.js
508 ms
slick.min.js
517 ms
add-to-cart-variation.min.js
650 ms
single-product.min.js
630 ms
jquery.zoom.min.js
630 ms
jquery.flexslider.min.js
624 ms
photoswipe-ui-default.min.js
604 ms
frontend.js
597 ms
jquery.smartmenus.min.js
564 ms
jquery.sticky.min.js
561 ms
sourcebuster.min.js
547 ms
order-attribution.min.js
525 ms
webpack-pro.runtime.min.js
511 ms
webpack.runtime.min.js
504 ms
frontend-modules.min.js
497 ms
wp-polyfill-inert.min.js
528 ms
regenerator-runtime.min.js
530 ms
wp-polyfill.min.js
504 ms
hooks.min.js
590 ms
i18n.min.js
645 ms
frontend.min.js
570 ms
core.min.js
619 ms
frontend.min.js
604 ms
elements-handlers.min.js
516 ms
frontend.min.js
498 ms
parallax-gallery.min.js
536 ms
hotips.min.js
571 ms
Screenshot-2020-06-25-at-14.26.07.png
381 ms
MSR57864.jpg
770 ms
MSR58321-Edit.jpg
756 ms
MSR57504.jpg
760 ms
red_logo.png
54 ms
BebasNeue-Regular.ttf
293 ms
fa-solid-900.woff
510 ms
fa-brands-400.woff
432 ms
eicons.woff
365 ms
783668575
219 ms
d
75 ms
d
131 ms
d
462 ms
d
569 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
176 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
177 ms
KFOmCnqEu92Fr1Mu4mxM.woff
210 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
226 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
210 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
227 ms
api.js
63 ms
woocommerce-smallscreen.css
79 ms
dpht.co.uk 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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Links do not have a discernible name
dpht.co.uk 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
dpht.co.uk 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dpht.co.uk 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 Dpht.co.uk 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.
dpht.co.uk
Open Graph data is detected on the main page of Dpht. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: