Tools & Wizards About Us
core72dc.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

core72dc.com

Core 72 | Be Extraordinary. Cool. Comfortable. Core.

Page Load Speed

1.7 sec in total

First Response

120 ms

Resources Loaded

1.1 sec

Page Rendered

423 ms

core72dc.com screenshot

About Website

Click here to check amazing Core 72 Dc content. Otherwise, check out these important facts you probably never knew about core72dc.com

Locally owned women's activewear boutique located in Chevy Chase and Cathedral Commons, Washington D.C.

Visit core72dc.com

Key Findings

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

Performance Metrics

core72dc.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.181

67/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

core72dc.com

120 ms

core72dc.com

111 ms

all.min.css

18 ms

v4-shims.min.css

34 ms

cnss.css

54 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 81% of them (57 requests) were addressed to the original Core72dc.com, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (634 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 215.0 kB (4%)

Content Size

6.1 MB

After Optimization

5.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Core72dc.com main page is 6.1 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. Only a small number of websites need less resources to load. Images take 5.7 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 88.2 kB

  • Original 114.8 kB
  • After minification 113.2 kB
  • After compression 26.7 kB

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

Image Optimization

-2%

Potential reduce by 124.3 kB

  • Original 5.7 MB
  • After minification 5.6 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. Core 72 Dc images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 279 B

  • Original 132.7 kB
  • After minification 132.7 kB
  • After compression 132.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 2.2 kB

  • Original 106.8 kB
  • After minification 104.8 kB
  • After compression 104.5 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. Core72dc.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 34 (58%)

Requests Now

59

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

core72dc.com

core72dc.com

120 ms

core72dc.com

core72dc.com

111 ms

all.min.css

all.min.css

18 ms

v4-shims.min.css

v4-shims.min.css

34 ms

cnss.css

cnss.css

54 ms

dashicons.min.css

dashicons.min.css

22 ms

theme-my-login.css

theme-my-login.css

44 ms

style.min.css

style.min.css

40 ms

6-layout.css

6-layout.css

26 ms

style.css

style.css

35 ms

all.min.css

all.min.css

43 ms

v4-shims.min.css

v4-shims.min.css

54 ms

responsive.css

responsive.css

52 ms

jquery.min.js

jquery.min.js

61 ms

jquery-migrate.min.js

jquery-migrate.min.js

84 ms

cnss.js

cnss.js

83 ms

breeze-prefetch-links.min.js

breeze-prefetch-links.min.js

84 ms

wonderplugincarouselskins.js

wonderplugincarouselskins.js

85 ms

wonderplugincarousel.js

wonderplugincarousel.js

84 ms

core.min.js

core.min.js

85 ms

mouse.min.js

mouse.min.js

85 ms

sortable.min.js

sortable.min.js

84 ms

6-layout.js

6-layout.js

85 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

85 ms

navigation.js

navigation.js

86 ms

global.js

global.js

86 ms

jquery.scrollTo.js

jquery.scrollTo.js

87 ms

custom.js

custom.js

87 ms

css

css

41 ms

lazyload.min.js

lazyload.min.js

86 ms

gtm.js

gtm.js

154 ms

analytics.js

analytics.js

134 ms

css

css

18 ms

body-background.jpg

body-background.jpg

13 ms

header-top-background.png

header-top-background.png

14 ms

core72-logo.png

core72-logo.png

130 ms

menu-toggle-backgound.png

menu-toggle-backgound.png

13 ms

Untitled-design-74-300x300.png

Untitled-design-74-300x300.png

13 ms

Untitled-design-75-300x300.png

Untitled-design-75-300x300.png

131 ms

Untitled-design-76-300x300.png

Untitled-design-76-300x300.png

134 ms

IMG_7759-scaled.jpg

IMG_7759-scaled.jpg

133 ms

IMG_6261.jpg

IMG_6261.jpg

135 ms

IMG_6200.jpg

IMG_6200.jpg

135 ms

IMG_6130-scaled.jpg

IMG_6130-scaled.jpg

136 ms

IMG_7564.jpg

IMG_7564.jpg

147 ms

IMG_7640-scaled.jpg

IMG_7640-scaled.jpg

138 ms

IMG_7686-scaled.jpg

IMG_7686-scaled.jpg

140 ms

IMG_7184-scaled.jpg

IMG_7184-scaled.jpg

143 ms

IMG_6999-scaled.jpg

IMG_6999-scaled.jpg

141 ms

facebook.png

facebook.png

144 ms

twitter.png

twitter.png

147 ms

insta.png

insta.png

148 ms

footer_seperator_vertical.png

footer_seperator_vertical.png

438 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

556 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

575 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmYWRl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmYWRl.woff

631 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRl.woff

634 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRl.woff

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRl.woff

634 ms

fa-solid-900.woff

fa-solid-900.woff

554 ms

fa-solid-900.woff

fa-solid-900.woff

554 ms

fa-regular-400.woff

fa-regular-400.woff

552 ms

fa-regular-400.woff

fa-regular-400.woff

552 ms

froogaloop2.min.js

froogaloop2.min.js

559 ms

iframe_api

iframe_api

618 ms

fontello.css

fontello.css

559 ms

slider_title_bg.png

slider_title_bg.png

141 ms

arrows-42-60-0.png

arrows-42-60-0.png

173 ms

collect

collect

101 ms

js

js

53 ms

www-widgetapi.js

www-widgetapi.js

5 ms

Accessibility Review

core72dc.com accessibility score

98

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

core72dc.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

core72dc.com SEO score

91

Search Engine Optimization Advices

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 uses 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 Core72dc.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 Core72dc.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

core72dc.com

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