7.3 sec in total
143 ms
6.5 sec
597 ms
Click here to check amazing City View Memoriam content. Otherwise, check out these important facts you probably never knew about cityviewmemoriam.com
Everything we do at City View Mortuary is done as a tribute or memoriam to those who have departed this life. Let us join you in creating lasting tribute.
Visit cityviewmemoriam.comWe analyzed Cityviewmemoriam.com page load time and found that the first response time was 143 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
cityviewmemoriam.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value26.7 s
0/100
25%
Value20.4 s
0/100
10%
Value12,560 ms
0/100
30%
Value0.003
100/100
15%
Value26.9 s
0/100
10%
143 ms
2195 ms
198 ms
134 ms
251 ms
Our browser made a total of 164 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cityviewmemoriam.com, 79% (129 requests) were made to Cityviewmortuary.com and 9% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Cityviewmortuary.com.
Page size can be reduced by 265.6 kB (9%)
2.9 MB
2.7 MB
In fact, the total size of Cityviewmemoriam.com main page is 2.9 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. 85% 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. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 72.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 72.1 kB or 80% of the original size.
Potential reduce by 177.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. City View Memoriam images are well optimized though.
Potential reduce by 11.7 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 4.1 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. Cityviewmemoriam.com has all CSS files already compressed.
Number of requests can be reduced by 133 (91%)
146
13
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of City View Memoriam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 113 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
cityviewmemoriam.com
143 ms
www.cityviewmortuary.com
2195 ms
gtm.js
198 ms
wp-emoji-release.min.js
134 ms
google-review.css
251 ms
style.min.css
375 ms
style-frontend-pro.1.20.2.css
354 ms
mediaelementplayer-legacy.min.css
379 ms
wp-mediaelement.min.css
381 ms
style.css
381 ms
font-awesome.min.css
359 ms
style.min.css
684 ms
style.css
676 ms
dripicons.css
660 ms
kiko-all.css
656 ms
font-awesome-5.min.css
672 ms
stylesheet.min.css
713 ms
print.css
669 ms
style_dynamic_callback.php
1274 ms
responsive.min.css
682 ms
style_dynamic_responsive_callback.php
1224 ms
js_composer.min.css
1067 ms
css
205 ms
core-dashboard.min.css
838 ms
style.css
842 ms
wpac-time.js
844 ms
jquery.min.js
849 ms
jquery-migrate.min.js
850 ms
js
197 ms
front-end-free.1.20.2.js
1060 ms
core.min.js
1091 ms
accordion.min.js
1057 ms
menu.min.js
1111 ms
regenerator-runtime.min.js
1109 ms
wp-polyfill.min.js
1112 ms
dom-ready.min.js
1112 ms
hooks.min.js
1162 ms
i18n.min.js
1163 ms
a11y.min.js
1168 ms
autocomplete.min.js
1170 ms
api.js
604 ms
controlgroup.min.js
1154 ms
analytics.js
492 ms
js
191 ms
js
488 ms
checkboxradio.min.js
1061 ms
button.min.js
1039 ms
datepicker.min.js
932 ms
mouse.min.js
948 ms
resizable.min.js
957 ms
draggable.min.js
959 ms
dialog.min.js
963 ms
droppable.min.js
671 ms
progressbar.min.js
670 ms
selectable.min.js
691 ms
sortable.min.js
698 ms
slider.min.js
698 ms
spinner.min.js
679 ms
tooltip.min.js
667 ms
tabs.min.js
537 ms
effect.min.js
555 ms
style.css
566 ms
effect-blind.min.js
769 ms
effect-bounce.min.js
925 ms
effect-clip.min.js
925 ms
collect
52 ms
collect
65 ms
effect-drop.min.js
719 ms
effect-explode.min.js
739 ms
effect-fade.min.js
706 ms
effect-fold.min.js
707 ms
effect-highlight.min.js
706 ms
effect-pulsate.min.js
686 ms
effect-size.min.js
686 ms
effect-scale.min.js
685 ms
effect-shake.min.js
687 ms
effect-slide.min.js
636 ms
effect-transfer.min.js
639 ms
doubletaptogo.js
634 ms
modernizr.min.js
649 ms
jquery.appear.js
613 ms
hoverIntent.min.js
597 ms
counter.js
596 ms
easypiechart.js
596 ms
mixitup.js
595 ms
jquery.prettyPhoto.js
578 ms
jquery.fitvids.js
562 ms
jquery.flexslider-min.js
552 ms
mediaelement-and-player.min.js
573 ms
mediaelement-migrate.min.js
546 ms
wp-mediaelement.min.js
544 ms
infinitescroll.min.js
539 ms
jquery.waitforimages.js
527 ms
jquery.form.min.js
517 ms
waypoints.min.js
520 ms
jplayer.min.js
515 ms
bootstrap.carousel.js
509 ms
skrollr.js
710 ms
Chart.min.js
690 ms
js
317 ms
testimonial-holder-2-1.png
1042 ms
jquery.easing.1.3.js
465 ms
loader.js
376 ms
swap.js
477 ms
abstractBaseClass.js
413 ms
jquery.countdown.js
411 ms
jquery.multiscroll.min.js
410 ms
jquery.justifiedGallery.min.js
386 ms
bigtext.js
385 ms
jquery.sticky-kit.min.js
382 ms
owl.carousel.min.js
541 ms
typed.js
540 ms
fluidvids.min.js
539 ms
jquery.carouFredSel-6.2.1.min.js
537 ms
lemmon-slider.min.js
541 ms
jquery.fullPage.min.js
541 ms
jquery.mousewheel.min.js
619 ms
jquery.touchSwipe.min.js
615 ms
jquery.isotope.min.js
596 ms
packery-mode.pkgd.min.js
595 ms
jquery.stretch.js
595 ms
imagesloaded.js
594 ms
rangeslider.min.js
661 ms
jquery.event.move.js
662 ms
jquery.twentytwenty.js
659 ms
swiper.min.js
705 ms
TweenLite.min.js
658 ms
ScrollToPlugin.min.js
657 ms
smoothPageScroll.min.js
734 ms
default_dynamic_callback.php
1623 ms
default.min.js
735 ms
comment-reply.min.js
718 ms
js_composer_front.min.js
716 ms
qode-like.min.js
731 ms
index.php
2179 ms
back-whole.jpg
903 ms
conversion_async.js
119 ms
cityview-logo-dark-197.png
579 ms
cityview-logo-dark-111.png
577 ms
Main-page-photo-2-1.png
1333 ms
city-view-vimeo-photo-800x508.png
899 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
290 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf
288 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf
291 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf
291 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf
291 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf
290 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf
337 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf
337 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf
294 ms
wlpogwHKFkZgtmSR3NB0oRJfajhfK_M.ttf
337 ms
wlprgwHKFkZgtmSR3NB0oRJfajDqDuNc_LA.ttf
336 ms
wlp2gwHKFkZgtmSR3NB0oRJfYQhW.ttf
335 ms
wlppgwHKFkZgtmSR3NB0oRJXsCxGAtNV.ttf
336 ms
wlppgwHKFkZgtmSR3NB0oRJX1C1GAtNV.ttf
336 ms
fontawesome-webfont.woff
590 ms
back-papaya.jpg
659 ms
call-tracking_7.js
122 ms
212 ms
233 ms
36 ms
wcm
43 ms
41 ms
recaptcha__en.js
11 ms
cityviewmemoriam.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
cityviewmemoriam.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
Page has valid source maps
cityviewmemoriam.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Cityviewmemoriam.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 Cityviewmemoriam.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.
cityviewmemoriam.com
Open Graph data is detected on the main page of City View Memoriam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: