5.6 sec in total
1.1 sec
4 sec
526 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 1.1 sec 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.4 s
0/100
10%
Value23.9 s
0/100
25%
Value16.7 s
0/100
10%
Value490 ms
59/100
30%
Value0.827
4/100
15%
Value35.1 s
0/100
10%
1105 ms
288 ms
275 ms
361 ms
275 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 90% of them (99 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.1 sec) belongs to the original domain Decenthome.com.
Page size can be reduced by 3.2 MB (55%)
5.8 MB
2.6 MB
In fact, the total size of Decenthome.com main page is 5.8 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. Javascripts take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 65.3 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 65.3 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.6 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.6 MB or 74% of the original size.
Potential reduce by 486.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 486.8 kB or 80% of the original size.
Number of requests can be reduced by 82 (84%)
98
16
The browser has sent 98 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 58 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
www.decenthome.com
1105 ms
style.min.css
288 ms
style-wpzoom-social-icons.css
275 ms
style.css
361 ms
style.css
275 ms
style.css
277 ms
css
32 ms
style.min.css
493 ms
wpzoom-socicon.css
457 ms
genericons.css
372 ms
academicons.min.css
373 ms
font-awesome-3.min.css
379 ms
dashicons.min.css
538 ms
wpzoom-social-icons-styles.css
464 ms
elementor-icons.min.css
466 ms
frontend-lite.min.css
475 ms
swiper.min.css
554 ms
post-5.css
559 ms
post-7.css
563 ms
backend.css
569 ms
backend.css
588 ms
css
27 ms
fontawesome.min.css
720 ms
solid.min.css
652 ms
jquery.min.js
823 ms
jquery-migrate.min.js
661 ms
frontend.js
671 ms
slick.css
582 ms
slick-theme.css
651 ms
frontend.css
659 ms
wp-polyfill-inert.min.js
666 ms
regenerator-runtime.min.js
678 ms
wp-polyfill.min.js
888 ms
autop.min.js
802 ms
blob.min.js
802 ms
block-serialization-default-parser.min.js
803 ms
react.min.js
803 ms
hooks.min.js
818 ms
deprecated.min.js
852 ms
dom.min.js
705 ms
react-dom.min.js
705 ms
escape-html.min.js
701 ms
element.min.js
726 ms
is-shallow-equal.min.js
693 ms
i18n.min.js
687 ms
keycodes.min.js
685 ms
priority-queue.min.js
688 ms
compose.min.js
628 ms
private-apis.min.js
647 ms
redux-routine.min.js
684 ms
data.min.js
672 ms
html-entities.min.js
659 ms
shortcode.min.js
625 ms
blocks.min.js
711 ms
dom-ready.min.js
645 ms
a11y.min.js
694 ms
moment.min.js
689 ms
date.min.js
1105 ms
primitives.min.js
621 ms
rich-text.min.js
637 ms
warning.min.js
685 ms
components.min.js
766 ms
url.min.js
630 ms
api-fetch.min.js
619 ms
keyboard-shortcuts.min.js
642 ms
commands.min.js
772 ms
notices.min.js
676 ms
preferences-persistence.min.js
564 ms
preferences.min.js
594 ms
style-engine.min.js
641 ms
token-list.min.js
648 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf
19 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf
27 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf
43 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf
50 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf
67 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf
67 ms
wordcount.min.js
654 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
66 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
51 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
50 ms
block-editor.min.js
1027 ms
core-data.min.js
766 ms
script.js
668 ms
plugins.min.js
671 ms
scripts.min.js
673 ms
social-icons-widget-frontend.js
727 ms
slick.min.js
729 ms
frontend.js
704 ms
webpack.runtime.min.js
736 ms
frontend-modules.min.js
849 ms
waypoints.min.js
771 ms
core.min.js
754 ms
frontend.min.js
739 ms
slick.woff
742 ms
fa-solid-900.woff
820 ms
mainlogo-01.png
779 ms
about-1024x681-2.jpg
971 ms
AS-DH-GRAND-MOSQUE-NEW-CAPTIAL-167-1536x1152.jpg
792 ms
4-1536x1152.jpg
1004 ms
DSCF7429-1536x1152.jpg
853 ms
cropped-certificates-1024x680-2-768x460.jpg
788 ms
process-1024x681-1-768x511.jpg
796 ms
certificates-1024x680-2-300x199.jpg
800 ms
about-1024x681-2-300x200.jpg
819 ms
5-1024x768-1-300x225.jpg
813 ms
2-3-300x200.jpg
831 ms
4-1024x683-1-300x200.jpg
808 ms
process-1024x681-1-300x200.jpg
789 ms
certificates-1024x680-2.jpg
816 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: