Tools & Wizards About Us
glitznashville.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

glitznashville.com

Glitz Nashville | Designer Prom, Bridal and more

Page Load Speed

1.5 sec in total

First Response

88 ms

Resources Loaded

738 ms

Page Rendered

625 ms

glitznashville.com screenshot

About Website

Visit glitznashville.com now to see the best up-to-date Glitz Nashville content for United States and also check out these interesting facts you probably never knew about glitznashville.com

Find the perfect designer prom or wedding dress for your formal or bridal event at Glitz Nashville in Nashville, Tennessee!

Visit glitznashville.com

Key Findings

We analyzed Glitznashville.com page load time and found that the first response time was 88 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

glitznashville.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.8 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value1,040 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value21.4 s

1/100

10%

Network Requests Diagram

www.glitznashville.com

88 ms

zpe8iod.css

155 ms

js

62 ms

theme.min.css

33 ms

theme.min.js

176 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 41% of them (24 requests) were addressed to the original Glitznashville.com, 34% (20 requests) were made to Dy9ihb9itgy3g.cloudfront.net and 15% (9 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (380 ms) relates to the external source Dy9ihb9itgy3g.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 291.2 kB (8%)

Content Size

3.4 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Glitznashville.com main page is 3.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 100.7 kB

  • Original 110.8 kB
  • After minification 66.5 kB
  • After compression 10.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 44.3 kB, which is 40% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 100.7 kB or 91% of the original size.

Image Optimization

-2%

Potential reduce by 57.6 kB

  • Original 2.5 MB
  • After minification 2.4 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Glitz Nashville images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 88.6 kB

  • Original 653.4 kB
  • After minification 653.4 kB
  • After compression 564.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 88.6 kB or 14% of the original size.

CSS Optimization

-23%

Potential reduce by 44.3 kB

  • Original 196.7 kB
  • After minification 196.7 kB
  • After compression 152.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Glitznashville.com needs all CSS files to be minified and compressed as it can save up to 44.3 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (11%)

Requests Now

47

After Optimization

42

  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Glitz Nashville. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.glitznashville.com

www.glitznashville.com

88 ms

zpe8iod.css

zpe8iod.css

155 ms

js

js

62 ms

theme.min.css

theme.min.css

33 ms

theme.min.js

theme.min.js

176 ms

js

js

136 ms

p.css

p.css

33 ms

events.js

events.js

325 ms

formal-black.png

formal-black.png

129 ms

56771__d_f.740.webp

56771__d_f.740.webp

294 ms

56484__d_f.740.webp

56484__d_f.740.webp

380 ms

56482__d_f.740.webp

56482__d_f.740.webp

291 ms

56465__d_f.740.webp

56465__d_f.740.webp

291 ms

56462__d_f.740.webp

56462__d_f.740.webp

293 ms

55720__-pink-52311.740.webp

55720__-pink-52311.740.webp

295 ms

ew35103__f_23.740.webp

ew35103__f_23.740.webp

291 ms

ew35086__f_d.740.webp

ew35086__f_d.740.webp

293 ms

ew35010__f__2600.740.webp

ew35010__f__2600.740.webp

294 ms

ew35002__f_d1320.740.webp

ew35002__f_d1320.740.webp

294 ms

7533__d_f.740.webp

7533__d_f.740.webp

296 ms

7524__d_f.740.webp

7524__d_f.740.webp

298 ms

7521__d_f.740.webp

7521__d_f.740.webp

298 ms

7501__d_f.740.webp

7501__d_f.740.webp

297 ms

54027__bright__pink__47988.740.jpg

54027__bright__pink__47988.740.jpg

297 ms

38377__d_f.740.webp

38377__d_f.740.webp

298 ms

26197__d_f.740.webp

26197__d_f.740.webp

299 ms

25919__d_f.740.webp

25919__d_f.740.webp

299 ms

7413__d_f_1.740.webp

7413__d_f_1.740.webp

300 ms

22314__d_f.740.webp

22314__d_f.740.webp

301 ms

bridal-white.png

bridal-white.png

184 ms

main-logo

main-logo

183 ms

ee5a71dc465c47bb950858edde539d97.webp

ee5a71dc465c47bb950858edde539d97.webp

216 ms

16ad1946f6e74fc0b3092154a5725f27.webp

16ad1946f6e74fc0b3092154a5725f27.webp

286 ms

40df301d80354bf2804f5a6d7fc321a5.webp

40df301d80354bf2804f5a6d7fc321a5.webp

287 ms

3cdf19ff371045b792af4534b7860aa0.webp

3cdf19ff371045b792af4534b7860aa0.webp

293 ms

2aa326ab77f34a488eae31ef19d1cbda.webp

2aa326ab77f34a488eae31ef19d1cbda.webp

286 ms

5933815c8c7c495fa0151f985657f1fe.webp

5933815c8c7c495fa0151f985657f1fe.webp

285 ms

about-bg.jpg

about-bg.jpg

288 ms

about-bg-mobile.jpg

about-bg-mobile.jpg

290 ms

formal_occasion.jpg

formal_occasion.jpg

311 ms

glitz_experience.jpg

glitz_experience.jpg

312 ms

experience2.jpg

experience2.jpg

301 ms

IMG_5240_homepage_resized.jpg

IMG_5240_homepage_resized.jpg

312 ms

experience4.jpg

experience4.jpg

300 ms

girls.jpg

girls.jpg

301 ms

brides-by-glitz-black.png

brides-by-glitz-black.png

310 ms

d

d

133 ms

d

d

181 ms

d

d

211 ms

d

d

204 ms

icomoon.ttf

icomoon.ttf

201 ms

Syvo-Icomoon.ttf

Syvo-Icomoon.ttf

209 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

223 ms

d

d

111 ms

d

d

112 ms

d

d

137 ms

d

d

154 ms

gtm.js

gtm.js

123 ms

main.MTcyODg5NjdlMA.js

main.MTcyODg5NjdlMA.js

68 ms

Accessibility Review

glitznashville.com accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[role]s are not contained by their required parent element

High

[aria-*] attributes are not valid or misspelled

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

glitznashville.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

glitznashville.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glitznashville.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Glitznashville.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

glitznashville.com

Open Graph data is detected on the main page of Glitz Nashville. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: