5.3 sec in total
830 ms
4.1 sec
386 ms
Welcome to decenthome.com homepage info - get ready to check Decent Home best content right away, or after learning these important things about decenthome.com
Visit decenthome.comWe analyzed Decenthome.com page load time and found that the first response time was 830 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
decenthome.com performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value13.2 s
0/100
25%
Value11.9 s
4/100
10%
Value380 ms
70/100
30%
Value1.88
0/100
15%
Value34.9 s
0/100
10%
830 ms
279 ms
284 ms
375 ms
285 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 90% of them (98 requests) were addressed to the original Decenthome.com, 8% (9 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Decenthome.com.
Page size can be reduced by 3.1 MB (54%)
5.6 MB
2.6 MB
In fact, the total size of Decenthome.com main page is 5.6 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. 60% of websites need less resources to load. Javascripts take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 64.8 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 64.8 kB or 79% of the original size.
Potential reduce by 17.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. Decent Home images are well optimized though.
Potential reduce by 2.5 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 2.5 MB or 74% of the original size.
Potential reduce by 488.8 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. Decenthome.com needs all CSS files to be minified and compressed as it can save up to 488.8 kB or 80% of the original size.
Number of requests can be reduced by 81 (84%)
97
16
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Decent Home. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
www.decenthome.com
830 ms
style.min.css
279 ms
style-wpzoom-social-icons.css
284 ms
style.css
375 ms
style.css
285 ms
style.css
285 ms
css
33 ms
style.min.css
472 ms
wpzoom-socicon.css
369 ms
genericons.css
368 ms
academicons.min.css
374 ms
font-awesome-3.min.css
478 ms
dashicons.min.css
551 ms
wpzoom-social-icons-styles.css
461 ms
elementor-icons.min.css
462 ms
frontend-lite.min.css
655 ms
swiper.min.css
553 ms
post-5.css
553 ms
post-7.css
569 ms
backend.css
565 ms
backend.css
641 ms
css
29 ms
fontawesome.min.css
643 ms
solid.min.css
648 ms
jquery.min.js
753 ms
jquery-migrate.min.js
667 ms
frontend.js
732 ms
slick.css
652 ms
slick-theme.css
652 ms
frontend.css
662 ms
react.min.js
763 ms
react-jsx-runtime.min.js
764 ms
autop.min.js
764 ms
blob.min.js
765 ms
block-serialization-default-parser.min.js
765 ms
hooks.min.js
768 ms
deprecated.min.js
768 ms
dom.min.js
832 ms
react-dom.min.js
836 ms
escape-html.min.js
648 ms
element.min.js
660 ms
is-shallow-equal.min.js
667 ms
i18n.min.js
671 ms
keycodes.min.js
647 ms
priority-queue.min.js
650 ms
compose.min.js
649 ms
private-apis.min.js
660 ms
redux-routine.min.js
582 ms
data.min.js
584 ms
html-entities.min.js
628 ms
dom-ready.min.js
633 ms
a11y.min.js
560 ms
rich-text.min.js
575 ms
shortcode.min.js
582 ms
blocks.min.js
859 ms
moment.min.js
630 ms
date.min.js
1023 ms
primitives.min.js
554 ms
warning.min.js
572 ms
components.min.js
763 ms
url.min.js
624 ms
api-fetch.min.js
561 ms
keyboard-shortcuts.min.js
580 ms
commands.min.js
647 ms
notices.min.js
639 ms
preferences-persistence.min.js
563 ms
preferences.min.js
628 ms
style-engine.min.js
630 ms
token-list.min.js
656 ms
wordcount.min.js
667 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf
16 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf
22 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf
34 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf
40 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf
42 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf
41 ms
block-editor.min.js
762 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
41 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
42 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
41 ms
core-data.min.js
718 ms
wp-polyfill.min.js
719 ms
script.js
682 ms
plugins.min.js
690 ms
scripts.min.js
750 ms
social-icons-widget-frontend.js
738 ms
slick.min.js
752 ms
frontend.js
760 ms
webpack.runtime.min.js
699 ms
frontend-modules.min.js
741 ms
waypoints.min.js
744 ms
core.min.js
727 ms
frontend.min.js
753 ms
slick.woff
759 ms
fa-solid-900.woff
722 ms
mainlogo-01.png
741 ms
about-1024x681-2.jpg
744 ms
AS-DH-GRAND-MOSQUE-NEW-CAPTIAL-167-1536x1152.jpg
866 ms
4-1536x1152.jpg
847 ms
DSCF7429-1536x1152.jpg
984 ms
cropped-certificates-1024x680-2-768x460.jpg
726 ms
process-1024x681-1-768x511.jpg
730 ms
certificates-1024x680-2-300x199.jpg
663 ms
about-1024x681-2-300x200.jpg
740 ms
5-1024x768-1-300x225.jpg
728 ms
2-3-300x200.jpg
672 ms
4-1024x683-1-300x200.jpg
691 ms
process-1024x681-1-300x200.jpg
674 ms
certificates-1024x680-2.jpg
704 ms
decenthome.com 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
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
decenthome.com 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
decenthome.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Decenthome.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 Decenthome.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.
decenthome.com
Open Graph description is not detected on the main page of Decent Home. 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: