Tools & Wizards About Us
northenddallas.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

northenddallas.com

NorthEnd

Page Load Speed

2.1 sec in total

First Response

119 ms

Resources Loaded

747 ms

Page Rendered

1.2 sec

northenddallas.com screenshot

About Website

Click here to check amazing North End Dallas content for United States. Otherwise, check out these important facts you probably never knew about northenddallas.com

NorthEnd is an active, walkable destination located in Dallas’ urban core. One of the largest developments approved in Dallas, this site anchors and amplifies

Visit northenddallas.com

Key Findings

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

Performance Metrics

northenddallas.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value21.5 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

northend.com

119 ms

style.min.css

21 ms

theme.min.css

36 ms

custom-frontend-lite.min.css

61 ms

post-7.css

46 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Northenddallas.com, 14% (13 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Northend1.wpengine.com. The less responsive or slowest element that took the longest time to load (291 ms) relates to the external source Northend.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 192.6 kB (5%)

Content Size

3.8 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Northenddallas.com main page is 3.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 119.7 kB

  • Original 146.3 kB
  • After minification 142.4 kB
  • After compression 26.6 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 119.7 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 50.2 kB

  • Original 3.0 MB
  • After minification 2.9 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. North End Dallas images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 15.5 kB

  • Original 600.7 kB
  • After minification 600.7 kB
  • After compression 585.2 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

-8%

Potential reduce by 7.2 kB

  • Original 94.2 kB
  • After minification 94.1 kB
  • After compression 87.0 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. Northenddallas.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (84%)

Requests Now

76

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

northend.com

northend.com

119 ms

style.min.css

style.min.css

21 ms

theme.min.css

theme.min.css

36 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

61 ms

post-7.css

post-7.css

46 ms

elementor-icons.min.css

elementor-icons.min.css

56 ms

swiper.min.css

swiper.min.css

58 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

70 ms

post-2.css

post-2.css

67 ms

post-16.css

post-16.css

69 ms

post-17.css

post-17.css

70 ms

post-14.css

post-14.css

72 ms

style.css

style.css

73 ms

css

css

46 ms

fontawesome.min.css

fontawesome.min.css

74 ms

solid.min.css

solid.min.css

73 ms

wpgmza_data.js

wpgmza_data.js

72 ms

jquery.min.js

jquery.min.js

88 ms

jquery-migrate.min.js

jquery-migrate.min.js

81 ms

js

js

81 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

82 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

78 ms

ol.css

ol.css

80 ms

open-layers.css

open-layers.css

81 ms

font-awesome.min.css

font-awesome.min.css

160 ms

fa-5to4.css

fa-5to4.css

162 ms

common.css

common.css

162 ms

remodal.css

remodal.css

162 ms

remodal-default-theme.css

remodal-default-theme.css

163 ms

jquery.dataTables.min.css

jquery.dataTables.min.css

164 ms

components.css

components.css

165 ms

compat.css

compat.css

166 ms

owl.carousel.min.css

owl.carousel.min.css

167 ms

owl.theme.default.min.css

owl.theme.default.min.css

168 ms

featherlight.min.css

featherlight.min.css

167 ms

dataTables.responsive.css

dataTables.responsive.css

168 ms

components.css

components.css

169 ms

animations.min.css

animations.min.css

172 ms

hello-frontend.min.js

hello-frontend.min.js

177 ms

jquery.sticky.min.js

jquery.sticky.min.js

173 ms

imagesloaded.min.js

imagesloaded.min.js

159 ms

ol.js

ol.js

153 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

136 ms

dataTables.responsive.js

dataTables.responsive.js

135 ms

jquery-cookie.js

jquery-cookie.js

129 ms

remodal.min.js

remodal.min.js

124 ms

pep.js

pep.js

124 ms

text.js

text.js

123 ms

pako_deflate.min.js

pako_deflate.min.js

122 ms

wp-google-maps-pro.min.js

wp-google-maps-pro.min.js

291 ms

owl.carousel.js

owl.carousel.js

121 ms

featherlight.min.js

featherlight.min.js

121 ms

polyline.js

polyline.js

191 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

279 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

276 ms

webpack.runtime.min.js

webpack.runtime.min.js

277 ms

frontend-modules.min.js

frontend-modules.min.js

279 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

275 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

277 ms

wp-polyfill.min.js

wp-polyfill.min.js

200 ms

hooks.min.js

hooks.min.js

199 ms

i18n.min.js

i18n.min.js

198 ms

frontend.min.js

frontend.min.js

197 ms

waypoints.min.js

waypoints.min.js

197 ms

core.min.js

core.min.js

197 ms

frontend.min.js

frontend.min.js

199 ms

elements-handlers.min.js

elements-handlers.min.js

195 ms

northend-logo-white.svg

northend-logo-white.svg

195 ms

urban-arboretum-header-min-2.jpg

urban-arboretum-header-min-2.jpg

197 ms

northend-favicon-green-2.png

northend-favicon-green-2.png

196 ms

people-place-header-min-2.jpg

people-place-header-min-2.jpg

202 ms

mixed-use-network-header-min-2.jpg

mixed-use-network-header-min-2.jpg

197 ms

northend-new-urban-ecosystem-2-min.png

northend-new-urban-ecosystem-2-min.png

187 ms

NorthEnd-Site-Plan-V4.jpg

NorthEnd-Site-Plan-V4.jpg

188 ms

220921_DNE_Hart-Howerton_View_09-2.jpg

220921_DNE_Hart-Howerton_View_09-2.jpg

189 ms

hunt-re-logo-white-new-500.png

hunt-re-logo-white-new-500.png

185 ms

placeholder.png

placeholder.png

186 ms

camphorpro-regular.woff

camphorpro-regular.woff

171 ms

camphorpro-light.woff

camphorpro-light.woff

171 ms

camphorpro-medium.woff

camphorpro-medium.woff

171 ms

camphorpro-bold.woff

camphorpro-bold.woff

171 ms

eicons.woff

eicons.woff

62 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODH7alwg.ttf

68 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7alwg.ttf

68 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7alwg.ttf

97 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

105 ms

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYkqUcKWmT.ttf

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYkqUcKWmT.ttf

105 ms

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYoKUcKWmT.ttf

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYoKUcKWmT.ttf

106 ms

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYzKUcKWmT.ttf

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYzKUcKWmT.ttf

107 ms

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYEqUcKWmT.ttf

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYEqUcKWmT.ttf

104 ms

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYkqQcKWmT.ttf

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYkqQcKWmT.ttf

106 ms

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYTKIcKWmT.ttf

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYTKIcKWmT.ttf

109 ms

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYdaIcKWmT.ttf

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYdaIcKWmT.ttf

109 ms

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYEqIcKWmT.ttf

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYEqIcKWmT.ttf

107 ms

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYO6IcKWmT.ttf

KFOOCniXp96a4Tc2DaTeuDAoKsE617JFc49knOIYdjTYO6IcKWmT.ttf

109 ms

Accessibility Review

northenddallas.com accessibility score

87

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

northenddallas.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

northenddallas.com SEO score

93

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

Image elements do not have [alt] attributes

Mobile Friendly

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

Impact

Issue

High

Document uses legible font sizes

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 Northenddallas.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 Northenddallas.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

northenddallas.com

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