nashville.com

nashville.com is SSL secured

Free website and domain report on nashville.com

Last Updated: 6th April, 2023 Update Now
Overview

Snoop Summary for nashville.com

This is a free and comprehensive report about nashville.com. The domain nashville.com is currently hosted on a server located in United States with the IP address 192.163.193.61, where USD is the local currency and the local language is English. Nashville.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If nashville.com was to be sold it would possibly be worth $946 USD (based on the daily revenue potential of the website over a 24 month period). Nashville.com receives an estimated 450 unique visitors every day - a decent amount of traffic! This report was last updated 6th April, 2023.

About nashville.com

Site Preview: nashville.com nashville.com
Title: Nashville.com Official Guide to Nashville, Tennessee
Description: Nashville.com is your official guide to the best of Nashville hotels, attractions, activities, calendar of events, music, real estate and tickets.
Keywords and Tags: public information
Related Terms: airbnb nashville, main street nashville, nashville hotels, nashville sc, nashville sounds, nashville state community college, official events calendar, pollstar nashville, tn commercial litigation in nashville, topgolf nashville
Fav Icon:
Age: Over 30 years old
Domain Created: 14th April, 1993
Domain Updated: 28th February, 2019
Domain Expires: 15th April, 2023
Review

Snoop Score

2/5

Valuation

$946 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,960,211
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 450
Monthly Visitors: 13,697
Yearly Visitors: 164,250
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $39 USD
Yearly Revenue: $468 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: nashville.com 13
Domain Name: nashville 9
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.27 seconds
Load Time Comparison: Faster than 66% of sites

PageSpeed Insights

Avg. (All Categories) 72
Performance 65
Accessibility 77
Best Practices 80
SEO 92
Progressive Web App 45
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.nashville.com/
Updated: 27th April, 2021

2.27 seconds
First Contentful Paint (FCP)
31%
58%
11%

0.00 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on desktop
65

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for nashville.com. This includes details about optimizing page load times which can result in a better user experience.

Other

Estimated Input Latency — 30 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive nashville.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://nashville.com/
http/1.1
0
1207.2119996883
989
0
301
text/html
https://www.nashville.com/
h2
1207.9169997014
1451.669999864
18804
76807
200
text/html
Document
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
h2
1467.0579996891
1583.2109996118
45230
440319
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/event-tickets/common/src/resources/css/common-skeleton.min.css
h2
1467.2469999641
1562.9119998775
2629
12612
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/event-tickets/common/src/resources/css/tooltip.min.css
h2
1467.3889996484
1531.2369996682
902
1634
200
text/css
Stylesheet
https://www.nashville.com/wp-includes/css/dist/block-library/style.min.css
h2
1467.563000042
1794.611999765
9009
58171
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/contact-form-7/includes/css/styles.css
h2
1467.7459998056
1531.9559997879
1255
2630
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/mashsharer/assets/css/mashsb.min.css
h2
1467.9089998826
1778.0839996412
28903
46819
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/taqyeem-buttons/assets/style.css
h2
1468.3499997482
1779.2579997331
1419
4142
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/taqyeem/style.css
h2
1468.5629997402
1767.1609995887
1978
6907
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/wp-job-manager-indeed-integration/assets/css/frontend.css
h2
1468.6929997988
1826.1859999038
535
368
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/wp-job-manager/assets/dist/css/job-listings.css
h2
1468.868999742
1816.7729997076
1677
8455
200
text/css
Stylesheet
https://www.nashville.com/wp-content/themes/sahifa/style.css
h2
1469.0729998983
1839.1899997368
37087
201125
200
text/css
Stylesheet
https://www.nashville.com/wp-content/themes/sahifa/css/ilightbox/dark-skin/skin.css
h2
1469.2150000483
1813.6259997264
1643
7289
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto%3A100%2C100italic%2C300%2C300italic%2Cregular%2Citalic%2C500%2C500italic%2C700%2C700italic%2C900%2C900italic&display=swap
h2
1469.4129996933
1487.3709999956
1944
26497
200
text/css
Stylesheet
https://www.nashville.com/wp-content/cache/busting/1/sccss.css
h2
1469.550000038
1793.8859998249
900
1782
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/jetpack/css/jetpack.css
h2
1469.6700000204
1932.6059999876
14051
77191
200
text/css
Stylesheet
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
h2
1469.7819999419
1815.6029996462
31255
89496
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/jquery/jquery-migrate.min.js
h2
1469.8709999211
1534.4419996254
4507
11224
200
application/javascript
Script
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
h2
1470.0939999893
1609.7099999897
268666
990305
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/apbct-public.min.js?apbct_ver=5.156
h2
1470.215999987
1786.3389998674
2375
5179
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk-modal.min.js
h2
1470.7779996097
1778.631999623
1378
3088
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk_nocache.min.js
h2
1470.8869997412
1535.3589998558
1847
3769
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/mashsharer/assets/js/mashsb.min.js
h2
1471.1670000106
1534.8829999566
1871
4428
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/taqyeem/js/tie.js
h2
1471.3369999081
1779.7749997117
1209
2622
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/si-captcha-for-wordpress/captcha/si_captcha.js?ver=1619536527
h2
1471.4489998296
1803.0159999616
717
685
200
application/javascript
Script
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
h2
2051.0879997164
2238.2099996321
120067
119778
200
image/jpeg
Image
https://hotels.nashville.com/154530/searchbox/444745
h2
1840.7179997303
2151.4729997143
10347
35533
200
text/html
Script
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
h2
1934.002999682
2146.954999771
715408
3671850
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/vendor/wp-polyfill.min.js
h2
2049.1419997998
2180.8099998161
34580
99310
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/hooks.min.js
h2
2049.3059996516
2115.4930000193
2643
6937
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/i18n.min.js
h2
2049.4749997742
2127.5589996949
4194
10166
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/vendor/lodash.min.js
h2
2049.6109998785
2128.147999756
26102
72805
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/url.min.js
h2
2049.9689998105
2173.1650000438
3402
8620
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/api-fetch.min.js
h2
2050.1779997721
2117.5099997781
3811
12412
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/contact-form-7/includes/js/index.js
h2
2050.3269997425
2116.2899998017
3576
10946
200
application/javascript
Script
https://gdc.indeed.com/ads/apiresults.js
h2
2050.4629998468
2120.2879999764
2757
515
200
application/javascript
Script
https://www.nashville.com/wp-content/themes/sahifa/js/tie-scripts.js
h2
2050.6090000272
2239.4869998097
21716
74081
200
application/javascript
Script
https://www.nashville.com/wp-content/themes/sahifa/js/ilightbox.packed.js
h2
2050.7319997996
2240.1649998501
25313
79789
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/wp-embed.min.js
h2
2050.8559998125
2119.4400000386
1102
1426
200
application/javascript
Script
https://www.nashville.com/wp-content/themes/sahifa/js/search.js
h2
2050.9909996763
2120.6829999574
3973
15010
200
application/javascript
Script
https://stats.wp.com/e-202117.js
h2
2051.3399997726
2066.7359996587
3325
8972
200
application/javascript
Script
https://www.nashville.com/wp-admin/admin-ajax.php?0.7264316059231253
h2
2046.1009996943
3209.0039998293
589
64
200
text/html
XHR
https://www.nashville.com/wp-content/themes/sahifa/images/patterns/body-bg10.png
h2
2055.5340000428
2278.4909997135
470
185
200
image/png
Image
https://www.nashville.com/wp-content/themes/sahifa/images/stripe.png
h2
2063.0779997446
2238.9349997975
377
93
200
image/png
Image
https://www.nashville.com/wp-content/themes/sahifa/fonts/fontawesome/fontawesome-webfont.woff2?v=4.6.3
h2
2063.7260000221
2290.3939997777
72174
71896
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
2063.9059999958
2067.0649996027
11612
11048
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
2064.0779999085
2072.1269999631
11596
11032
200
font/woff2
Font
https://www.nashville.com/wp-content/themes/sahifa/fonts/BebasNeue/BebasNeue-webfont.woff
h2
2064.5929998718
2182.3669997975
20152
19996
200
font/woff
Font
https://www.nashville.com/wp-content/uploads/2019/03/Jason-Aldean-310x165.png
h2
2093.9659997821
2183.5339996032
70211
69924
200
image/png
Image
https://www.nashville.com/wp-content/uploads/2021/04/cb703b0b-9662-4004-a23c-fb355d9575ea-310x165.jpeg
h2
2094.168999698
2174.6119996533
12028
11740
200
image/jpeg
Image
https://www.nashville.com/wp-content/uploads/2019/12/Tenille-Arts--310x165.jpg
h2
2094.4359996356
2175.1089999452
11356
11068
200
image/jpeg
Image
https://www.nashville.com/wp-content/uploads/2021/04/b1ed10eb-4a85-4c95-b161-ff0143925846-310x165.jpg
h2
2094.5889996365
2241.0649997182
14061
13773
200
image/jpeg
Image
https://www.nashville.com/wp-content/uploads/2019/01/luke-bryan1-310x165.jpg
h2
2095.0479996391
2240.6919999048
7899
7612
200
image/jpeg
Image
https://nashville.com/wp-content/uploads/2019/03/1a.jpg
h2
2095.3460000455
2400.3729997203
21824
21536
200
image/jpeg
Image
https://hotels.nashville.com/Script/JsMapper.ashx?key=/areas/responsivesearchbox.js&cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
h2
2162.1069996618
2683.8819999248
83829
199614
200
text/javascript
Script
https://hotels.nashville.com/SearchBox/Style/hc_searchbox.css?cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
h2
2162.5289996155
2392.3009997234
6485
34238
200
text/css
Stylesheet
https://hotels.nashville.com/SearchBox/Image/Light/poweredby_hotelscombined.png?cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
h2
2166.937999893
2326.0470000096
2248
1901
200
image/png
Image
https://www.facebook.com/plugins/likebox.php?href=https://www.facebook.com/nashvillecom&width=300&height=250&show_faces=true&header=false&stream=false&show_border=false
h2
2169.8799999431
2265.5109995976
14856
45797
200
text/html
Document
https://www.nashville.com/wp-content/uploads/2020/03/cma-fest-tickets-nashville-tn.jpg
h2
2185.128999874
2289.7609998472
14444
14156
200
image/jpeg
Image
https://www.nashville.com/wp-content/uploads/2021/02/nashville-predators-nashville-tn.jpg
h2
2185.4129997082
2260.7249999419
20868
20580
200
image/jpeg
Image
https://nashville.com/wp-content/uploads/2017/06/General-Jackson-Showboat-300x200.jpg
h2
2185.6080000289
2486.5249996074
20679
20391
200
image/jpeg
Image
https://nashville.com/wp-content/uploads/2019/07/Nashville-real-estate-condo.jpg
h2
2185.9229998663
2488.4539996274
57115
56827
200
image/jpeg
Image
https://nashville.com/wp-content/uploads/2018/08/nashville-twitter.jpg
h2
2186.2129997462
2528.0279996805
52687
52399
200
image/jpeg
Image
https://www.nashville.com/wp-content/uploads/2020/03/nashville-logo-footer.jpg
h2
2187.028999906
2279.547999613
27610
27322
200
image/jpeg
Image
https://www.nashville.com/wp-content/plugins/google-website-translator/images/all.png
h2
2193.6399997212
2291.5989998728
42102
41815
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v27/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
h2
2218.0289998651
2221.7339999042
13240
12676
200
font/woff2
Font
https://fonts.googleapis.com/css?family=Roboto
h2
2431.1619997025
2445.6479996443
1266
2022
200
text/css
Stylesheet
data
2656.8709998392
2656.9319996051
0
38
200
image/webp
Image
https://netdna.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
h2
2693.6009996571
2725.1499998383
78495
77160
200
font/woff2
Font
https://pixel.wp.com/g.gif?v=ext&j=1%3A9.6.1&blog=164618556&post=337&tz=-5&srv=www.nashville.com&host=www.nashville.com&ref=&fcp=2122&rand=0.12667349414303808
h2
2882.961999625
2897.0839995891
186
50
200
image/gif
Image
https://www.facebook.com/rsrc.php/v3/yM/l/0,cross/marMItmZNfV.css?_nc_x=Ij3Wp8lg5Kz
h2
2926.0029997677
2955.7219999842
6511
25947
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
h2
2926.2599996291
2959.9269996397
74539
278747
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yS/r/-T_3VWEC8Ch.js?_nc_x=Ij3Wp8lg5Kz
h2
2926.5419999138
2956.2169997953
20233
64459
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3iEpO4/yQ/l/en_US/N1Ujot6efHX.js?_nc_x=Ij3Wp8lg5Kz
h2
2926.8089998513
3099.6479997411
37059
130984
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/y3/r/oYH4_Q4OBVP.js?_nc_x=Ij3Wp8lg5Kz
h2
2926.9689996727
2956.627999898
2321
5581
200
application/x-javascript
Script
https://scontent-ort2-1.xx.fbcdn.net/v/t31.18172-0/p130x130/18121327_982107008592512_7022462997231347794_o.jpg?_nc_cat=106&ccb=1-3&_nc_sid=dd9801&_nc_ohc=gCusWhmgdWIAX9ioOoy&_nc_ht=scontent-ort2-1.xx&tp=6&oh=f96b7e7b19ec617bf76545bc8c0fda64&oe=60AD9B29
h2
3187.1619997546
3216.5249995887
14643
14115
200
image/jpeg
Image
https://scontent-ort2-1.xx.fbcdn.net/v/t1.18169-1/cp0/p50x50/16998779_941575679312312_3202032139526362869_n.png?_nc_cat=105&ccb=1-3&_nc_sid=dbb9e7&_nc_ohc=o1HASb8dy9EAX98Ds7w&_nc_ht=scontent-ort2-1.xx&tp=30&oh=235ab9994a87ea1347ba5639a1eb29ba&oe=60AD7254
h2
3210.2459999733
3241.0729997791
3083
2554
200
image/png
Image
https://cdn.datahc.com/Images/hc_calendar_button.gif
h2
3148.5309996642
3257.3549998924
325
43
200
image/gif
Image
https://cdn.datahc.com/SearchBox/Image/Light/hc_icon_calendar_modern.png?
h2
3154.902999755
3271.7879996635
1370
1064
200
image/png
Image
https://www.facebook.com/rsrc.php/v3/y_/r/ApcBOUT5FoS.png
h2
3248.7200000323
3276.2129995972
1095
573
200
image/png
Image
https://gdc.indeed.com/rpc/apilog?a=apiresults
h2
3295.7019996829
3336.1990000121
2522
0
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1480.484
7.388
1492.427
6.273
1611.69
13.4
1866.713
6.885
1963.061
117.159
2080.235
41.541
2129.934
12.095
2177.42
7.002
2185.753
9.817
2195.647
16.814
2218.618
21.842
2242.536
8.215
2259.483
23.342
2287.645
7.716
2297.57
9.085
2306.957
6.242
2313.511
376.135
2689.807
45.036
2743.941
11.985
2758.821
23.244
2783.616
7.304
2791.169
150.864
2942.112
7.908
2955.952
7.739
2965.013
7.179
2977.726
100.073
3077.849
8.407
3089.491
85.358
3180.215
8.602
3193.567
15.484
3212.525
23.703
3236.524
21.369
3258.104
23.974
3284.871
12.433
3303.129
18.982
3930.152
9.497
3940.803
27.091
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 36 KiB
Images can slow down the page's load time. Nashville.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
119778
22581
https://www.nashville.com/wp-content/uploads/2021/02/nashville-predators-nashville-tn.jpg
20580
8293
https://www.nashville.com/wp-content/uploads/2020/03/cma-fest-tickets-nashville-tn.jpg
14156
5705
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Nashville.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 36 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Nashville.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
@charset "UTF-8"; .ihf-eureka-stylesheet { display: none !important; } ...
222267
31253
https://www.nashville.com/wp-content/themes/sahifa/style.css
37087
5663
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Nashville.com should consider minifying JS files.
Remove unused CSS — Potential savings of 336 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Nashville.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
@charset "UTF-8"; .ihf-eureka-stylesheet { display: none !important; } ...
222267
222173
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
45230
45117
https://www.nashville.com/wp-content/themes/sahifa/style.css
37087
33624
https://www.nashville.com/wp-content/plugins/mashsharer/assets/css/mashsb.min.css
28903
28903
https://www.nashville.com/wp-content/plugins/jetpack/css/jetpack.css
14051
14051
Efficiently encode images — Potential savings of 69 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://nashville.com/wp-content/uploads/2019/07/Nashville-real-estate-condo.jpg
56827
31462
https://nashville.com/wp-content/uploads/2018/08/nashville-twitter.jpg
52399
27362
https://www.nashville.com/wp-content/uploads/2020/03/nashville-logo-footer.jpg
27322
12238
Serve images in next-gen formats — Potential savings of 191 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.nashville.com/wp-content/uploads/2019/03/Jason-Aldean-310x165.png
69924
62846
https://nashville.com/wp-content/uploads/2019/07/Nashville-real-estate-condo.jpg
56827
40693
https://nashville.com/wp-content/uploads/2018/08/nashville-twitter.jpg
52399
35911
https://www.nashville.com/wp-content/plugins/google-website-translator/images/all.png
41815
26883
https://www.nashville.com/wp-content/uploads/2020/03/nashville-logo-footer.jpg
27322
20066
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
119778
9426
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 240 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.nashville.com/
244.75
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Nashville.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://nashville.com/
190
https://www.nashville.com/
0
Preload key requests — Potential savings of 130 ms
Key requests can be preloaded by using '<link rel=preload>'. Nashville.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://hotels.nashville.com/SearchBox/Style/hc_searchbox.css?cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
126
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 31 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk_nocache.min.js
9575
https://www.nashville.com/wp-content/themes/sahifa/js/ilightbox.packed.js
8502
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
7344
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
5897
https://www.nashville.com/
167
https://www.nashville.com/wp-includes/js/dist/hooks.min.js
64
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
0

Diagnostics

Avoids enormous network payloads — Total size was 2,265 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
715408
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
268666
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
120067
https://hotels.nashville.com/Script/JsMapper.ashx?key=/areas/responsivesearchbox.js&cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
83829
https://netdna.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
78495
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
74539
https://www.nashville.com/wp-content/themes/sahifa/fonts/fontawesome/fontawesome-webfont.woff2?v=4.6.3
72174
https://www.nashville.com/wp-content/uploads/2019/03/Jason-Aldean-310x165.png
70211
https://nashville.com/wp-content/uploads/2019/07/Nashville-real-estate-condo.jpg
57115
https://nashville.com/wp-content/uploads/2018/08/nashville-twitter.jpg
52687
Avoid chaining critical requests — 43 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Nashville.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 34 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
Zone
Measure
2368.81
0.7
Zone:ZoneAwarePromise
Measure
2369.66
4.17
Zone:toString
Measure
2373.865
0.12
Zone:util
Measure
2374.095
0.16
Zone:legacy
Measure
2374.265
0.035
Zone:timers
Measure
2374.31
0.245
Zone:requestAnimationFrame
Measure
2374.57
0.08
Zone:blocking
Measure
2374.66
0.095
Zone:EventTarget
Measure
2374.765
0.67
Zone:MutationObserver
Measure
2375.455
0.24
Zone:IntersectionObserver
Measure
2375.71
0.16
Zone:FileReader
Measure
2375.89
0.195
Zone:on_property
Measure
2376.105
26.665
Zone:customElements
Measure
2402.825
0.335
Zone:XHR
Measure
2403.195
0.4
Zone:geolocation
Measure
2403.625
0.21
Zone:PromiseRejectionEvent
Measure
2403.865
0.135
Zone
Mark
2368.863
Zone:ZoneAwarePromise
Mark
2369.676
Zone:toString
Mark
2373.873
Zone:util
Mark
2374.103
Zone:legacy
Mark
2374.269
Zone:timers
Mark
2374.312
Zone:requestAnimationFrame
Mark
2374.572
Zone:blocking
Mark
2374.659
Zone:EventTarget
Mark
2374.765
Zone:MutationObserver
Mark
2375.46
Zone:IntersectionObserver
Mark
2375.716
Zone:FileReader
Mark
2375.895
Zone:on_property
Mark
2376.109
Zone:customElements
Mark
2402.832
Zone:XHR
Mark
2403.201
Zone:geolocation
Mark
2403.631
Zone:PromiseRejectionEvent
Mark
2403.866
JavaScript execution time — 0.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
406.473
320.25
57.22
https://www.nashville.com/
313.755
6.556
4.317
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
137.763
110.298
1.582
Unattributable
120.448
1.55
0.257
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
112.516
55.951
22.543
https://hotels.nashville.com/154530/searchbox/444745
66.359
44.997
0.914
Minimizes main-thread work — 1.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
710.313
Style & Layout
240.116
Other
188.631
Script Parsing & Compilation
129.337
Rendering
81.158
Parse HTML & CSS
77.711
Garbage Collection
30.911
Keep request counts low and transfer sizes small — 81 requests • 2,265 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
81
2319256
Script
29
1394055
Image
24
519270
Font
6
207269
Stylesheet
18
163424
Document
2
33660
Other
2
1578
Media
0
0
Third-party
24
1332282
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
174340
0
78495
0
39658
0
5279
0
3511
0
1695
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 4 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
2850
376
https://www.nashville.com/wp-includes/js/dist/vendor/wp-polyfill.min.js
3226
75
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
1890
59
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
3301
50

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 1.2 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 3.0 s
The time taken for the page to become fully interactive.
Total Blocking Time — 180 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 2.8 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 1.2 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 700 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Nashville.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
45230
350
https://www.nashville.com/wp-content/plugins/mashsharer/assets/css/mashsb.min.css
28903
120
https://www.nashville.com/wp-content/themes/sahifa/style.css
37087
80
https://fonts.googleapis.com/css?family=Roboto%3A100%2C100italic%2C300%2C300italic%2Cregular%2Citalic%2C500%2C500italic%2C700%2C700italic%2C900%2C900italic&display=swap
1944
230
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
31255
80
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
268666
320
Remove unused JavaScript — Potential savings of 641 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
715408
295916
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
268666
227832
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
74539
52395
https://hotels.nashville.com/Script/JsMapper.ashx?key=/areas/responsivesearchbox.js&cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
83829
47764
https://www.facebook.com/rsrc.php/v3iEpO4/yQ/l/en_US/N1Ujot6efHX.js?_nc_x=Ij3Wp8lg5Kz
37059
32614

Diagnostics

Avoid an excessive DOM size — 837 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
837
Maximum DOM Depth
Day
19
Maximum Child Elements
36

Metrics

Speed Index — 2.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.5 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.262
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 380 ms
Users could experience a delay when interacting with the page.

Diagnostics

Serve static assets with an efficient cache policy — 7 resources found
Nashville.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
0
715408
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
0
268666
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
0
45230
https://gdc.indeed.com/ads/apiresults.js
0
2757
https://hotels.nashville.com/154530/searchbox/444745
3600000
10347
https://scontent-ort2-1.xx.fbcdn.net/v/t31.18172-0/p130x130/18121327_982107008592512_7022462997231347794_o.jpg?_nc_cat=106&ccb=1-3&_nc_sid=dd9801&_nc_ohc=gCusWhmgdWIAX9ioOoy&_nc_ht=scontent-ort2-1.xx&tp=6&oh=f96b7e7b19ec617bf76545bc8c0fda64&oe=60AD9B29
1209600000
14643
https://scontent-ort2-1.xx.fbcdn.net/v/t1.18169-1/cp0/p50x50/16998779_941575679312312_3202032139526362869_n.png?_nc_cat=105&ccb=1-3&_nc_sid=dbb9e7&_nc_ohc=o1HASb8dy9EAX98Ds7w&_nc_ht=scontent-ort2-1.xx&tp=30&oh=235ab9994a87ea1347ba5639a1eb29ba&oe=60AD7254
1209600000
3083
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.nashville.com/wp-content/themes/sahifa/fonts/fontawesome/fontawesome-webfont.woff2?v=4.6.3
226.66799975559
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
8.0490000545979
https://www.nashville.com/wp-content/themes/sahifa/fonts/BebasNeue/BebasNeue-webfont.woff
117.7739999257
https://netdna.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
31.549000181258
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
77

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of nashville.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Nashville.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements
h4

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that nashville.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Modernizr
2.7.0
Leaflet
1.6.0+HEAD.0c81bdf
yepnope
D3
3.5.6
Hammer.js
2.0.7
FlexSlider
WordPress
5.7.1
core-js
core-js-global@2.6.11
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://nashville.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://cdn.datahc.com/Images/hc_calendar_button.gif
25 x 25
1 x 1
25 x 25

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk-modal.min.js
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk-modal.min.js.map
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk_nocache.min.js
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk_nocache.min.js.map
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/apbct-public.min.js?apbct_ver=5.156
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/apbct-public.min.js.map
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for nashville.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of nashville.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
45

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of nashville.com. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of nashville.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 65
Performance 21
Accessibility 77
Best Practices 87
SEO 90
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.nashville.com/
Updated: 27th April, 2021

2.77 seconds
First Contentful Paint (FCP)
29%
53%
18%

0.02 seconds
First Input Delay (FID)
97%
3%
0%

Simulate loading on mobile
21

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for nashville.com. This includes details about optimizing page load times which can result in a better user experience.

Opportunities

Minify CSS — Potential savings of 36 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Nashville.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
@charset "UTF-8"; .ihf-eureka-stylesheet { display: none !important; } ...
222267
31253
https://www.nashville.com/wp-content/themes/sahifa/style.css
37087
5663
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Nashville.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 250 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.nashville.com/
247.937
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Nashville.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://nashville.com/
630
https://www.nashville.com/
0
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 31 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk_nocache.min.js
9575
https://www.nashville.com/wp-content/themes/sahifa/js/ilightbox.packed.js
8502
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
7344
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
5897
https://www.nashville.com/
167
https://www.nashville.com/wp-includes/js/dist/hooks.min.js
64
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 2,076 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
715408
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
268665
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
120067
https://hotels.nashville.com/Script/JsMapper.ashx?key=/areas/responsivesearchbox.js&cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
83830
https://netdna.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
78352
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
74539
https://www.nashville.com/wp-content/themes/sahifa/fonts/fontawesome/fontawesome-webfont.woff2?v=4.6.3
72174
https://www.nashville.com/wp-content/uploads/2019/03/Jason-Aldean-310x165.png
70211
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
45229
https://www.nashville.com/wp-content/plugins/google-website-translator/images/all.png
42102
Avoid chaining critical requests — 43 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Nashville.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures — 34 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
Zone
Measure
2081.325
0.515
Zone:ZoneAwarePromise
Measure
2081.965
0.635
Zone:toString
Measure
2082.62
0.1
Zone:util
Measure
2082.835
0.16
Zone:legacy
Measure
2083.015
0.04
Zone:timers
Measure
2083.065
0.205
Zone:requestAnimationFrame
Measure
2083.28
0.1
Zone:blocking
Measure
2083.385
0.13
Zone:EventTarget
Measure
2083.53
0.715
Zone:MutationObserver
Measure
2084.27
0.235
Zone:IntersectionObserver
Measure
2084.515
0.135
Zone:FileReader
Measure
2084.665
0.165
Zone:on_property
Measure
2084.845
31.22
Zone:customElements
Measure
2116.105
0.245
Zone:XHR
Measure
2116.365
0.295
Zone:geolocation
Measure
2116.675
0.19
Zone:PromiseRejectionEvent
Measure
2116.885
0.095
Zone
Mark
2081.378
Zone:ZoneAwarePromise
Mark
2081.973
Zone:toString
Mark
2082.63
Zone:util
Mark
2082.842
Zone:legacy
Mark
2083.023
Zone:timers
Mark
2083.07
Zone:requestAnimationFrame
Mark
2083.29
Zone:blocking
Mark
2083.394
Zone:EventTarget
Mark
2083.536
Zone:MutationObserver
Mark
2084.28
Zone:IntersectionObserver
Mark
2084.524
Zone:FileReader
Mark
2084.672
Zone:on_property
Mark
2084.85
Zone:customElements
Mark
2116.119
Zone:XHR
Mark
2116.383
Zone:geolocation
Mark
2116.681
Zone:PromiseRejectionEvent
Mark
2116.891
Keep request counts low and transfer sizes small — 75 requests • 2,076 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
75
2125804
Script
29
1394105
Image
18
325862
Font
6
207125
Stylesheet
18
163618
Document
2
33532
Other
2
1562
Media
0
0
Third-party
24
1332163
Minimize third-party usage — Third-party code blocked the main thread for 20 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
174195
20.64
78352
0
39856
0
5253
0
3511
0
1694
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.13134399414062
0.019538077354431
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 13 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
14040
1297
https://www.nashville.com/wp-includes/js/dist/vendor/wp-polyfill.min.js
15425
412
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
8640
269
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
15837
248
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
7050
195
https://www.nashville.com/
1651
102
https://www.nashville.com/
1840
96
https://hotels.nashville.com/Script/JsMapper.ashx?key=/areas/responsivesearchbox.js&cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
15337
88
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
4140
77
https://hotels.nashville.com/154530/searchbox/444745
2881
74
Unattributable
655
61
https://www.facebook.com/rsrc.php/v3iEpO4/yQ/l/en_US/N1Ujot6efHX.js?_nc_x=Ij3Wp8lg5Kz
6990
60
https://www.nashville.com/
1753
53

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://nashville.com/
http/1.1
0
1046.9009999651
973
0
301
text/html
https://www.nashville.com/
h2
1047.6059999783
1294.5469999686
18804
76807
200
text/html
Document
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
h2
1321.5610000771
1440.4070000164
45229
440319
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/event-tickets/common/src/resources/css/common-skeleton.min.css
h2
1322.0740000252
1516.2270001601
2629
12612
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/event-tickets/common/src/resources/css/tooltip.min.css
h2
1322.3460000008
1524.5060001034
902
1634
200
text/css
Stylesheet
https://www.nashville.com/wp-includes/css/dist/block-library/style.min.css
h2
1322.4800000899
1587.1160000097
9009
58171
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/contact-form-7/includes/css/styles.css
h2
1322.7320001461
1399.2790000048
1255
2630
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/mashsharer/assets/css/mashsb.min.css
h2
1322.8730000556
1642.688000109
28903
46819
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/taqyeem-buttons/assets/style.css
h2
1323.2420000713
1417.3860000446
1419
4142
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/taqyeem/style.css
h2
1323.4290000983
1525.0600001309
1978
6907
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/wp-job-manager-indeed-integration/assets/css/frontend.css
h2
1323.6289999913
1523.4610000625
535
368
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/wp-job-manager/assets/dist/css/job-listings.css
h2
1323.779999977
1571.4879999869
1677
8455
200
text/css
Stylesheet
https://www.nashville.com/wp-content/themes/sahifa/style.css
h2
1323.9959999919
1467.2380001284
37087
201125
200
text/css
Stylesheet
https://www.nashville.com/wp-content/themes/sahifa/css/ilightbox/dark-skin/skin.css
h2
1324.1739999503
1525.7770000026
1643
7289
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Roboto%3A100%2C100italic%2C300%2C300italic%2Cregular%2Citalic%2C500%2C500italic%2C700%2C700italic%2C900%2C900italic&display=swap
h2
1324.3750000838
1345.7890001591
2111
32874
200
text/css
Stylesheet
https://www.nashville.com/wp-content/cache/busting/1/sccss.css
h2
1324.535000138
1525.4689999856
900
1782
200
text/css
Stylesheet
https://www.nashville.com/wp-content/plugins/jetpack/css/jetpack.css
h2
1324.6550001204
1647.8999999817
14051
77191
200
text/css
Stylesheet
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
h2
1324.8430001549
1629.7120000236
31255
89496
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/jquery/jquery-migrate.min.js
h2
1325.0980000012
1394.0360001288
4507
11224
200
application/javascript
Script
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
h2
1325.2610000782
1473.8270000089
268665
990305
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/apbct-public.min.js?apbct_ver=5.156
h2
1325.4289999604
1514.5860000048
2375
5179
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk-modal.min.js
h2
1325.6650001276
1515.4620001558
1378
3088
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk_nocache.min.js
h2
1325.8440000936
1578.0840001535
1847
3769
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/mashsharer/assets/js/mashsb.min.js
h2
1326.006000163
1395.206999965
1871
4428
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/taqyeem/js/tie.js
h2
1326.9879999571
1516.717000166
1209
2622
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/si-captcha-for-wordpress/captcha/si_captcha.js?ver=1619536527
h2
1327.1149999928
1394.7670001071
717
685
200
application/javascript
Script
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
h2
1787.003000034
1968.3829999994
120067
119778
200
image/jpeg
Image
https://hotels.nashville.com/154530/searchbox/444745
h2
1646.6610000934
1851.7289999872
10440
35533
200
text/html
Script
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
h2
1655.0430001225
1842.7000001539
715408
3671850
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/vendor/wp-polyfill.min.js
h2
1784.8839999642
1971.47400002
34580
99310
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/hooks.min.js
h2
1785.0669999607
1853.3710001502
2643
6937
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/i18n.min.js
h2
1785.2410001215
1852.7260001283
4194
10166
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/vendor/lodash.min.js
h2
1785.3680001572
1858.9399999473
26102
72805
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/url.min.js
h2
1785.5130000971
1853.0580000952
3402
8620
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/dist/api-fetch.min.js
h2
1785.6799999718
1858.511999948
3811
12412
200
application/javascript
Script
https://www.nashville.com/wp-content/plugins/contact-form-7/includes/js/index.js
h2
1785.845000064
1852.3930001538
3576
10946
200
application/javascript
Script
https://gdc.indeed.com/ads/apiresults.js
h2
1785.9390000813
1823.8360001706
2731
515
200
application/javascript
Script
https://www.nashville.com/wp-content/themes/sahifa/js/tie-scripts.js
h2
1786.0410001595
1859.4260001555
21716
74081
200
application/javascript
Script
https://www.nashville.com/wp-content/themes/sahifa/js/ilightbox.packed.js
h2
1786.3620000426
1859.9900000263
25313
79789
200
application/javascript
Script
https://www.nashville.com/wp-includes/js/wp-embed.min.js
h2
1786.6269999649
1852.111000102
1102
1426
200
application/javascript
Script
https://www.nashville.com/wp-content/themes/sahifa/js/search.js
h2
1786.8079999462
1854.084999999
3973
15010
200
application/javascript
Script
https://stats.wp.com/e-202117.js
h2
1787.1489999816
1803.9679999929
3325
8972
200
application/javascript
Script
https://www.nashville.com/wp-admin/admin-ajax.php?0.3866856280847597
h2
1781.0909999534
2825.5960000679
589
64
200
text/html
XHR
https://www.nashville.com/wp-content/themes/sahifa/images/patterns/body-bg10.png
h2
1802.3230000399
1874.4459999725
470
185
200
image/png
Image
https://www.nashville.com/wp-content/themes/sahifa/images/stripe.png
h2
1808.8080000598
1874.9910001643
377
93
200
image/png
Image
https://www.nashville.com/wp-content/themes/sahifa/fonts/fontawesome/fontawesome-webfont.woff2?v=4.6.3
h2
1809.4399999827
1912.5830000266
72174
71896
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2
h2
1810.9930001665
1814.8209999781
11611
11048
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
1811.6030001547
1814.5020001102
11596
11032
200
font/woff2
Font
https://www.nashville.com/wp-content/themes/sahifa/fonts/BebasNeue/BebasNeue-webfont.woff
h2
1812.2420001309
1909.5280000474
20152
19996
200
font/woff
Font
https://www.nashville.com/wp-content/uploads/2019/03/Jason-Aldean-310x165.png
h2
1843.734000111
1914.4099999685
70211
69924
200
image/png
Image
https://www.nashville.com/wp-content/uploads/2021/04/cb703b0b-9662-4004-a23c-fb355d9575ea-310x165.jpeg
h2
1849.9219999649
1973.1060001068
12028
11740
200
image/jpeg
Image
https://www.nashville.com/wp-content/uploads/2019/12/Tenille-Arts--310x165.jpg
h2
1850.0640001148
1970.8040000405
11356
11068
200
image/jpeg
Image
https://www.nashville.com/wp-content/uploads/2021/04/b1ed10eb-4a85-4c95-b161-ff0143925846-310x165.jpg
h2
1850.1930001657
1920.1440000907
14061
13773
200
image/jpeg
Image
https://www.nashville.com/wp-content/uploads/2019/01/luke-bryan1-310x165.jpg
h2
1850.3590000328
1915.0000000373
7899
7612
200
image/jpeg
Image
https://nashville.com/wp-content/uploads/2019/03/1a.jpg
h2
1850.4880000837
2092.6700001583
21824
21536
200
image/jpeg
Image
https://hotels.nashville.com/Script/JsMapper.ashx?key=/areas/responsivesearchbox.js&cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
h2
1888.7210001703
1972.4040001165
83830
199614
200
text/javascript
Script
https://hotels.nashville.com/SearchBox/Style/hc_searchbox.css?cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
h2
1888.8650001027
1965.8429999836
6481
34238
200
text/css
Stylesheet
https://hotels.nashville.com/SearchBox/Image/Light/poweredby_hotelscombined.png?cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
h2
1891.0420001484
2122.8120001033
2244
1901
200
image/png
Image
https://www.facebook.com/plugins/likebox.php?href=https://www.facebook.com/nashvillecom&width=300&height=250&show_faces=true&header=false&stream=false&show_border=false
h2
1894.9629999697
2057.5690001715
14728
45648
200
text/html
Document
https://www.nashville.com/wp-content/plugins/google-website-translator/images/all.png
h2
1911.082000006
1975.7620000746
42102
41815
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v27/KFOkCnqEu92Fr1Mu51xIIzIXKMny.woff2
h2
1936.8950000498
1940.7110000029
13240
12676
200
font/woff2
Font
https://fonts.googleapis.com/css?family=Roboto
h2
2145.1830000151
2159.7280001733
1298
2463
200
text/css
Stylesheet
data
2316.024000058
2316.1079999991
0
38
200
image/webp
Image
https://netdna.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
h2
2357.5659999624
2385.2180000395
78352
77160
200
font/woff2
Font
https://cdn.datahc.com/Images/hc_calendar_button.gif
h2
2619.5300000254
2635.0010000169
325
43
200
image/gif
Image
https://pixel.wp.com/g.gif?v=ext&j=1%3A9.6.1&blog=164618556&post=337&tz=-5&srv=www.nashville.com&host=www.nashville.com&ref=&fcp=1856&rand=0.5414612765858877
h2
2621.8820000067
2636.1569999717
186
50
200
image/gif
Image
https://cdn.datahc.com/SearchBox/Image/Light/hc_icon_calendar_modern.png?
h2
2627.0910000894
2724.4059999939
1369
1064
200
image/png
Image
https://www.facebook.com/rsrc.php/v3/yM/l/0,cross/marMItmZNfV.css?_nc_x=Ij3Wp8lg5Kz
h2
2714.7340001538
2746.0650000721
6511
25947
200
text/css
Stylesheet
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
h2
2715.0149999652
2748.7580000889
74539
278747
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/yS/r/-T_3VWEC8Ch.js?_nc_x=Ij3Wp8lg5Kz
h2
2715.2879999485
2749.8670001514
20233
64459
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3iEpO4/yQ/l/en_US/N1Ujot6efHX.js?_nc_x=Ij3Wp8lg5Kz
h2
2715.5000001658
2750.655000098
37042
130984
200
application/x-javascript
Script
https://www.facebook.com/rsrc.php/v3/y3/r/oYH4_Q4OBVP.js?_nc_x=Ij3Wp8lg5Kz
h2
2715.6700000633
2744.3790000398
2321
5581
200
application/x-javascript
Script
https://scontent-ort2-1.xx.fbcdn.net/v/t31.18172-0/p130x130/18121327_982107008592512_7022462997231347794_o.jpg?_nc_cat=106&ccb=1-3&_nc_sid=dd9801&_nc_ohc=gCusWhmgdWIAX8bJudD&_nc_ht=scontent-ort2-1.xx&tp=6&oh=d04b1816184ee06d1ca7e947f45b0f43&oe=60AD9B29
h2
2810.999999987
2839.6489999723
14643
14115
200
image/jpeg
Image
https://scontent-ort2-1.xx.fbcdn.net/v/t1.18169-1/cp0/p50x50/16998779_941575679312312_3202032139526362869_n.png?_nc_cat=105&ccb=1-3&_nc_sid=dbb9e7&_nc_ohc=o1HASb8dy9EAX8DDK4o&_nc_ht=scontent-ort2-1.xx&tp=30&oh=9ace6fdad28e446d52b5919479568d8e&oe=60AD7254
h2
2823.3460001647
2851.3919999823
3083
2554
200
image/png
Image
https://www.facebook.com/rsrc.php/v3/y_/r/ApcBOUT5FoS.png
h2
2877.7330000885
2907.2010000236
1095
573
200
image/png
Image
https://gdc.indeed.com/rpc/apilog?a=apiresults
h2
2919.2260000855
2999.6599999722
2522
0
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1344.277
12.084
1361.326
10.829
1489.148
19.125
1518.121
10.078
1701.156
134.332
1835.502
50.986
1893.139
9.211
1902.767
7.319
1913.501
5.285
1921.681
18.51
1942.362
11.719
1955.814
7.07
1970.742
26.289
1997.69
5.439
2005.226
16.903
2032.944
12.286
2045.717
324.361
2370.226
47.974
2418.803
10.242
2429.069
15.159
2448.765
43.788
2492.582
6.749
2500.855
206.233
2707.189
23.071
2732.082
7.3
2741.451
16.756
2764.025
5.924
2774.299
62.096
2868.996
48.754
2920.818
12.627
2933.481
11.137
2944.664
14.996
2960.018
5.245
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Metrics

Cumulative Layout Shift — 0.151
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Properly size images — Potential savings of 71 KiB
Images can slow down the page's load time. Nashville.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
119778
72289
Defer offscreen images — Potential savings of 41 KiB
Time to Interactive can be slowed down by resources on the page. Nashville.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.nashville.com/wp-content/plugins/google-website-translator/images/all.png
41815
41815
Remove unused CSS — Potential savings of 336 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Nashville.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
@charset "UTF-8"; .ihf-eureka-stylesheet { display: none !important; } ...
222267
222173
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
45229
45116
https://www.nashville.com/wp-content/themes/sahifa/style.css
37087
33903
https://www.nashville.com/wp-content/plugins/mashsharer/assets/css/mashsb.min.css
28903
28903
https://www.nashville.com/wp-content/plugins/jetpack/css/jetpack.css
14051
14051
Serve images in next-gen formats — Potential savings of 97 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.nashville.com/wp-content/uploads/2019/03/Jason-Aldean-310x165.png
69924
62846
https://www.nashville.com/wp-content/plugins/google-website-translator/images/all.png
41815
26883
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
119778
9426

Diagnostics

Avoid an excessive DOM size — 837 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
837
Maximum DOM Depth
Day
19
Maximum Child Elements
36
Reduce JavaScript execution time — 2.8 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
1404.376
1043.376
212.296
https://www.nashville.com/
1155.92
29.832
31.376
Unattributable
488.308
6.5
0.792
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
463.532
261.052
94.624
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
393.872
350.892
8.228
https://hotels.nashville.com/154530/searchbox/444745
331.984
192.272
26.524
https://www.facebook.com/plugins/likebox.php?href=https://www.facebook.com/nashvillecom&width=300&height=250&show_faces=true&header=false&stream=false&show_border=false
252.368
132.024
14.712
https://www.nashville.com/wp-includes/js/dist/vendor/wp-polyfill.min.js
190.428
177.22
12.696
https://hotels.nashville.com/Script/JsMapper.ashx?key=/areas/responsivesearchbox.js&cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
182.956
92.78
21.744
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
87.084
40.44
34.34
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
76.5
0
0
https://www.nashville.com/wp-includes/js/dist/vendor/lodash.min.js
51.056
42.96
8.096

Metrics

First Contentful Paint — 5.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 7.5 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 5.2 s
The timing of the largest text or image that is painted.
Time to Interactive — 15.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 1,390 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 14.1 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 1,300 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 5.2 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 650 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive nashville.com as laggy when the latency is higher than 0.05 seconds.
First Contentful Paint (3G) — 10859 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 3,450 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Nashville.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
45229
1380
https://www.nashville.com/wp-content/plugins/mashsharer/assets/css/mashsb.min.css
28903
600
https://www.nashville.com/wp-content/themes/sahifa/style.css
37087
600
https://fonts.googleapis.com/css?family=Roboto%3A100%2C100italic%2C300%2C300italic%2Cregular%2Citalic%2C500%2C500italic%2C700%2C700italic%2C900%2C900italic&display=swap
2111
780
https://www.nashville.com/wp-content/plugins/jetpack/css/jetpack.css
14051
300
https://www.nashville.com/wp-includes/js/jquery/jquery.min.js
31255
600
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
268665
1950
Remove unused JavaScript — Potential savings of 641 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
715408
295916
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
268665
227831
https://www.facebook.com/rsrc.php/v3/yM/r/s42o5npKlRj.js?_nc_x=Ij3Wp8lg5Kz
74539
52395
https://hotels.nashville.com/Script/JsMapper.ashx?key=/areas/responsivesearchbox.js&cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
83830
47736
https://www.facebook.com/rsrc.php/v3iEpO4/yQ/l/en_US/N1Ujot6efHX.js?_nc_x=Ij3Wp8lg5Kz
37042
32599
Preload key requests — Potential savings of 840 ms
Key requests can be preloaded by using '<link rel=preload>'. Nashville.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://hotels.nashville.com/SearchBox/Style/hc_searchbox.css?cdn=1.0.2021.110001-C499dfc9c7d460cc0873d428bebb8c100621f913c
841

Diagnostics

Serve static assets with an efficient cache policy — 7 resources found
Nashville.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
0
715408
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
0
268665
https://www.idxhome.com/service/resources/dist/wordpress/bundle.css?1619515334470
0
45229
https://gdc.indeed.com/ads/apiresults.js
0
2731
https://hotels.nashville.com/154530/searchbox/444745
3600000
10440
https://scontent-ort2-1.xx.fbcdn.net/v/t31.18172-0/p130x130/18121327_982107008592512_7022462997231347794_o.jpg?_nc_cat=106&ccb=1-3&_nc_sid=dd9801&_nc_ohc=gCusWhmgdWIAX8bJudD&_nc_ht=scontent-ort2-1.xx&tp=6&oh=d04b1816184ee06d1ca7e947f45b0f43&oe=60AD9B29
1209600000
14643
https://scontent-ort2-1.xx.fbcdn.net/v/t1.18169-1/cp0/p50x50/16998779_941575679312312_3202032139526362869_n.png?_nc_cat=105&ccb=1-3&_nc_sid=dbb9e7&_nc_ohc=o1HASb8dy9EAX8DDK4o&_nc_ht=scontent-ort2-1.xx&tp=30&oh=9ace6fdad28e446d52b5919479568d8e&oe=60AD7254
1209600000
3083
Minimize main-thread work — 5.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2491.368
Style & Layout
915.86
Other
760.596
Script Parsing & Compilation
545.392
Parse HTML & CSS
386.172
Rendering
221.632
Garbage Collection
126.024
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.nashville.com/wp-content/themes/sahifa/fonts/fontawesome/fontawesome-webfont.woff2?v=4.6.3
103.14300004393
https://fonts.gstatic.com/s/roboto/v27/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
2.8989999555051
https://www.nashville.com/wp-content/themes/sahifa/fonts/BebasNeue/BebasNeue-webfont.woff
97.285999916494
https://netdna.bootstrapcdn.com/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
27.652000077069
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.nashville.com/wp-content/uploads/2021/04/Nashville-Main1.jpg
77

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of nashville.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Nashville.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements
h4

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that nashville.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Modernizr
2.7.0
Leaflet
1.6.0+HEAD.0c81bdf
yepnope
D3
3.5.6
Hammer.js
2.0.7
FlexSlider
WordPress
5.7.1
core-js
core-js-global@2.6.11
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://nashville.com/
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.idxhome.com/service/resources/dist/wordpress/bundle.js?1619515334470
https://www.idxhome.com/eureka/ihf-eureka.js?1619515334470
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk-modal.min.js
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk-modal.min.js.map
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk_nocache.min.js
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/cleantalk_nocache.min.js.map
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/apbct-public.min.js?apbct_ver=5.156
https://www.nashville.com/wp-content/plugins/cleantalk-spam-protect/js/apbct-public.min.js.map
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for nashville.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of nashville.com on mobile screens.
Document uses legible font sizes — 99.7% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
#SB_8526d301f8 .hcsb_noDatesWrapper label
0.24%
11.7px
.plugin, .plugin button, .plugin input, .plugin label, .plugin select, .plugin td, .plugin textarea
0.04%
11px
#SB_8526d301f8, #SB_8526d301f8 div, #SB_8526d301f8 h1, #SB_8526d301f8 h2, #SB_8526d301f8 fieldset, #SB_8526d301f8 span, #SB_8526d301f8 img, #SB_8526d301f8 label, #SB_8526d301f8 select, #EX-SB_8526d301f8, #EX-SB_8526d301f8 div, #EX-SB_8526d301f8 h1, #EX-SB_8526d301f8 h2, #EX-SB_8526d301f8 fieldset, #EX-SB_8526d301f8 span, #EX-SB_8526d301f8 img, #EX-SB_8526d301f8 label, #EX-SB_8526d301f8 select
0.02%
0px
body, button, input, label, select, td, textarea
0.01%
0px
.post-thumbnail a
0.00%
0px
99.70%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 61% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
a
12x24
a
15x24
a
16x24
a
17x24
a
12x24
a
a
12x24
a
a
16x24
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a
a
22x16
a

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
50

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of nashville.com. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of nashville.com on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 192.163.193.61
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Unified Layer
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Moniker Online Services LLC 104.22.57.65
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: nashville.com
Issued By: cPanel, Inc. Certification Authority
Valid From: 7th March, 2021
Valid To: 5th June, 2021
Subject: CN = nashville.com
Hash: fc79bd0c
Issuer: CN = cPanel, Inc. Certification Authority
O = cPanel, Inc.
S = US
Version: 2
Serial Number: 144825851469465533305915476286601620712
Serial Number (Hex): 6CF471C4A23A4D94D64CCEFB3972ECE8
Valid From: 7th March, 2024
Valid To: 5th June, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:7E:03:5A:65:41:6B:A7:7E:0A:E1:B8:9D:08:EA:1D:8E:1D:6A:C7:65
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.comodoca.com/cPanelIncCertificationAuthority.crl

Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.52
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://crt.comodoca.com/cPanelIncCertificationAuthority.crt
OCSP - URI:http://ocsp.comodoca.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Mar 7 23:52:27.436 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:33:89:5F:5B:D0:09:3C:E1:E9:A4:57:20:
DD:61:6B:11:CA:89:36:A4:10:7F:FD:B1:0D:93:49:D4:
DE:0B:F0:FB:02:20:13:2F:EB:AD:44:FC:CF:90:B5:96:
33:2A:37:EF:76:91:24:F9:D3:9A:29:F0:93:6E:25:DC:
07:6C:8E:CA:5B:58
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Mar 7 23:52:27.335 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:94:19:93:5B:8D:98:0F:9D:B5:3C:5C:
55:24:B1:5A:C6:86:79:E3:4C:5E:B6:2F:17:16:D8:44:
A2:BA:EC:77:73:02:20:35:BB:54:80:AB:B2:5A:8A:FC:
B8:20:E9:D8:65:85:E0:C7:51:EC:F4:5D:1D:5B:08:92:
7C:BE:0A:7B:FC:03:09
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:mail.nashville.com
DNS:www.nashville.com
DNS:www.nashville.wog.poe.mybluehost.me
DNS:nashville.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
nashville.com. 192.163.193.61 IN 21599

NS Records

Host Nameserver Class TTL
nashville.com. ns.rackspace.com. IN 21599
nashville.com. ns2.rackspace.com. IN 21599

MX Records

Priority Host Server Class TTL
20 nashville.com. mx2.emailsrvr.com. IN 21599
10 nashville.com. mx1.emailsrvr.com. IN 21599

SOA Records

Domain Name Primary NS Responsible Email TTL
nashville.com. ns.rackspace.com. hostmaster.rackspace.com. 299

TXT Records

Host Value Class TTL
nashville.com. v=spf1 IN 299

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 27th April, 2021
Server: Apache
Cache-Control: max-age=0
Expires: 27th April, 2021
Content-Type: text/html; charset=UTF-8
Upgrade: h2,h2c
Connection: Upgrade
Last-Modified: 27th April, 2021
Vary: Accept-Encoding

Whois Lookup

Created: 14th April, 1993
Changed: 28th February, 2019
Expires: 15th April, 2023
Registrar: Moniker Online Services LLC
Status: clientTransferProhibited
Nameservers: ns.rackspace.com
ns2.rackspace.com
Owner Name: Michael Castello
Owner Organization: Castello Brothers, LLC
Owner Street: PO BOX 5537
Owner Post Code: 90296
Owner City: Playa del Rey
Owner State: CA
Owner Country: US
Owner Phone: +1.8887694764
Owner Email: michael@ccin.com
Admin Name: Michael Castello
Admin Organization: Castello Brothers, LLC
Admin Street: PO BOX 5537
Admin Post Code: 90296
Admin City: Playa del Rey
Admin State: CA
Admin Country: US
Admin Phone: +1.8887694764
Admin Email: michael@ccin.com
Tech Name: Michael Castello
Tech Organization: Castello Brothers, LLC
Tech Street: PO BOX 5537
Tech Post Code: 90296
Tech City: Playa del Rey
Tech State: CA
Tech Country: US
Tech Phone: +1.8887694764
Tech Email: michael@ccin.com
Billing Name: Michael Castello
Billing Organization: Castello Brothers, LLC
Billing Street: PO BOX 5537
Billing Post Code: 90296
Billing City: Playa del Rey
Billing State: CA
Billing Country: US
Billing Phone: +1.8887694764
Billing Fax: REDACTED FOR PRIVACY
Billing Email: michael@ccin.com
Full Whois: Domain Name: nashville.com
Registry Domain ID: 52337_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.moniker.com
Registrar URL: http://www.moniker.com
Updated Date: 2019-02-28T00:34:59Z
Creation Date: 1993-04-14T04:00:00Z
Registrar Registration Expiration Date: 2023-04-15T04:00:00Z
Registrar: Moniker Online Services LLC
Registrar IANA ID: 228
Registrar Abuse Contact Email: abusereport@moniker.com
Registrar Abuse Contact Phone: +1.9546071294
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: Michael Castello
Registrant Organization: Castello Brothers, LLC
Registrant Street: PO BOX 5537
Registrant City: Playa del Rey
Registrant State/Province: CA
Registrant Postal Code: 90296
Registrant Country: US
Registrant Phone: +1.8887694764
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: michael@ccin.com
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: Michael Castello
Admin Organization: Castello Brothers, LLC
Admin Street: PO BOX 5537
Admin City: Playa del Rey
Admin State/Province: CA
Admin Postal Code: 90296
Admin Country: US
Admin Phone: +1.8887694764
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: michael@ccin.com
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: Michael Castello
Tech Organization: Castello Brothers, LLC
Tech Street: PO BOX 5537
Tech City: Playa del Rey
Tech State/Province: CA
Tech Postal Code: 90296
Tech Country: US
Tech Phone: +1.8887694764
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: michael@ccin.com
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: Michael Castello
Billing Organization: Castello Brothers, LLC
Billing Street: PO BOX 5537
Billing City: Playa del Rey
Billing State/Province: CA
Billing Postal Code: 90296
Billing Country: US
Billing Phone: +1.8887694764
Billing Phone Ext:
Billing Fax: REDACTED FOR PRIVACY
Billing Fax Ext: REDACTED FOR PRIVACY
Billing Email: michael@ccin.com
Name Server: ns.rackspace.com
Name Server: ns2.rackspace.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: https://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-04-27T17:47:55Z <<<

For more information on Whois status codes, please visit https://www.icann.org/epp

To contact the registered registrant please proceed to:
https://www.domain-contact.org

Please register your domains at; http://www.moniker.com
This data is provided by MONIKER ONLINE SERVICES LLC.
for information purposes, and to assist persons obtaining information
about or related to domain name registration records.
MONIKER ONLINE SERVICES LLC. does not guarantee its accuracy.
By submitting a WHOIS query, you agree that you will use this data
only for lawful purposes and that, under no circumstances, you will
use this data to
1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via E-mail
(spam) or
2) enable high volume, automated, electronic processes that apply
to this WHOIS server.
These terms may be changed without prior notice.
By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
ns.rackspace.com 69.20.95.4
ns2.rackspace.com 65.61.188.4
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$1,000 USD 1/5
$1,030 USD 1/5
0/5
$102 USD 1/5
$965 USD 1/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
$208 USD

Sites hosted on the same IP address