Tools & Wizards About Us
whatsonindurham.net screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 79% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

whatsonindurham.net

What's on in Durham, Places to Stay and Eat, Attractions

Page Load Speed

7.1 sec in total

First Response

849 ms

Resources Loaded

5.7 sec

Page Rendered

577 ms

whatsonindurham.net screenshot

About Website

Visit whatsonindurham.net now to see the best up-to-date Whatsonin Durham content and also check out these interesting facts you probably never knew about whatsonindurham.net

Whether you’re looking for Things to see and do in Durham, events and attractions or are planning where to stay in Durham, everything you need is on whatsonindurham.net

Visit whatsonindurham.net

Key Findings

We analyzed Whatsonindurham.net page load time and found that the first response time was 849 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

whatsonindurham.net performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.2 s

0/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,900 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.647

9/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

www.whatsonindurham.net

849 ms

sbgp.css

241 ms

sbgp.css

341 ms

sbgp.css

339 ms

sbgp.css

352 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 65% of them (68 requests) were addressed to the original Whatsonindurham.net, 15% (16 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (957 ms) belongs to the original domain Whatsonindurham.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.0 kB (7%)

Content Size

2.7 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatsonindurham.net main page is 2.7 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. 60% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 104.8 kB

  • Original 127.7 kB
  • After minification 126.4 kB
  • After compression 22.9 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 104.8 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 51.7 kB

  • Original 2.1 MB
  • After minification 2.1 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. Whatsonin Durham images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 34.8 kB

  • Original 357.9 kB
  • After minification 357.9 kB
  • After compression 323.1 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

-3%

Potential reduce by 2.6 kB

  • Original 78.3 kB
  • After minification 78.3 kB
  • After compression 75.7 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. Whatsonindurham.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (60%)

Requests Now

86

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.whatsonindurham.net

www.whatsonindurham.net

849 ms

sbgp.css

sbgp.css

241 ms

sbgp.css

sbgp.css

341 ms

sbgp.css

sbgp.css

339 ms

sbgp.css

sbgp.css

352 ms

sbgp.css

sbgp.css

355 ms

sbgp.css

sbgp.css

352 ms

sbgp.css

sbgp.css

364 ms

sbgp.css

sbgp.css

455 ms

sbgp.css

sbgp.css

455 ms

sbgp.css

sbgp.css

471 ms

sbgp.css

sbgp.css

472 ms

sbgp.css

sbgp.css

473 ms

sbgp.css

sbgp.css

487 ms

sbgp.css

sbgp.css

570 ms

sbgp.css

sbgp.css

570 ms

css

css

52 ms

sbgp.css

sbgp.css

591 ms

sbgp.css

sbgp.css

590 ms

sbgp.css

sbgp.css

591 ms

sbgp.js

sbgp.js

858 ms

sbgp.js

sbgp.js

684 ms

cookieconsent.min.css

cookieconsent.min.css

47 ms

element.js

element.js

67 ms

wp-polyfill.min.js

wp-polyfill.min.js

689 ms

index.js

index.js

601 ms

swiped-events.min.js

swiped-events.min.js

601 ms

imagesloaded.min.js

imagesloaded.min.js

600 ms

effect.min.js

effect.min.js

692 ms

ditty-news-ticker.min.js

ditty-news-ticker.min.js

722 ms

wonderplugincarouselskins.js

wonderplugincarouselskins.js

720 ms

wonderplugincarousel.js

wonderplugincarousel.js

879 ms

jquery.rwdImageMaps.js

jquery.rwdImageMaps.js

847 ms

bootstrap-slider.js

bootstrap-slider.js

9 ms

api.js

api.js

40 ms

index.js

index.js

846 ms

wp-embed.min.js

wp-embed.min.js

878 ms

cookieconsent.min.js

cookieconsent.min.js

49 ms

cookieconsent.min.css

cookieconsent.min.css

3 ms

css

css

14 ms

css

css

17 ms

sdk.js

sdk.js

64 ms

analytics.js

analytics.js

157 ms

freecounterstat.php

freecounterstat.php

536 ms

1_1097_0_1_137AE9_160_ffffff_333333_08488D_1_ffffff_333333_0_6.png

1_1097_0_1_137AE9_160_ffffff_333333_08488D_1_ffffff_333333_0_6.png

470 ms

city-center-durham-nc.jpg

city-center-durham-nc.jpg

406 ms

search.png

search.png

213 ms

durham-north-carolina.jpg

durham-north-carolina.jpg

556 ms

durham-01.jpg

durham-01.jpg

763 ms

Duke-University-Chapel.png

Duke-University-Chapel.png

680 ms

Places-to-Stay-2.png

Places-to-Stay-2.png

449 ms

Golf-Clubs-2.jpg

Golf-Clubs-2.jpg

572 ms

Alley-Twenty-Six.png

Alley-Twenty-Six.png

497 ms

Bull-City-Burger-and-Brewery.png

Bull-City-Burger-and-Brewery.png

570 ms

The-Federal.png

The-Federal.png

622 ms

Tobacco-Road-Sports-Cafe.png

Tobacco-Road-Sports-Cafe.png

670 ms

Shopping.jpg

Shopping.jpg

692 ms

Hotels-150.jpg

Hotels-150.jpg

691 ms

Fitness-Gyms1.jpg

Fitness-Gyms1.jpg

745 ms

Golf-Clubs.jpg

Golf-Clubs.jpg

786 ms

Restaurants.jpg

Restaurants.jpg

798 ms

Spa-Massage.jpg

Spa-Massage.jpg

811 ms

Cafes-Delis.jpg

Cafes-Delis.jpg

812 ms

Biking1.jpg

Biking1.jpg

867 ms

Karting1.jpg

Karting1.jpg

874 ms

Aerial-Sports1.jpg

Aerial-Sports1.jpg

901 ms

Balloon-Flights1.jpg

Balloon-Flights1.jpg

919 ms

Yoga1.jpg

Yoga1.jpg

930 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xo.woff

180 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xo.woff

186 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xo.woff

185 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff

205 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYw.woff

204 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYw.woff

203 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff

203 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

895 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

957 ms

u-440qyriQwlOrhSvowK_l5-fCZK.woff

u-440qyriQwlOrhSvowK_l5-fCZK.woff

204 ms

u-4n0qyriQwlOrhSvowK_l521wRZWMf8.woff

u-4n0qyriQwlOrhSvowK_l521wRZWMf8.woff

203 ms

u-4n0qyriQwlOrhSvowK_l52xwNZWMf8.woff

u-4n0qyriQwlOrhSvowK_l52xwNZWMf8.woff

217 ms

css

css

59 ms

sdk.js

sdk.js

24 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

177 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

177 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

177 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

176 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

177 ms

u-4m0qyriQwlOrhSvowK_l5-eRZOf-Q.woff

u-4m0qyriQwlOrhSvowK_l5-eRZOf-Q.woff

181 ms

160 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

809 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

839 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

862 ms

collect

collect

49 ms

js

js

80 ms

cookieconsent.min.css

cookieconsent.min.css

271 ms

mhfontello.css

mhfontello.css

269 ms

froogaloop2.min.js

froogaloop2.min.js

218 ms

iframe_api

iframe_api

220 ms

www.whatsonindurham.net

www.whatsonindurham.net

275 ms

carouselarrows-32-32-0.png

carouselarrows-32-32-0.png

275 ms

arrows-32-32-0.png

arrows-32-32-0.png

262 ms

mhfontello.css

mhfontello.css

260 ms

bottomshadow-110-100-5.png

bottomshadow-110-100-5.png

135 ms

www-widgetapi.js

www-widgetapi.js

6 ms

playvideo-64-64-0.png

playvideo-64-64-0.png

128 ms

Accessibility Review

whatsonindurham.net accessibility score

92

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

Links do not have a discernible name

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

whatsonindurham.net 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

whatsonindurham.net SEO score

92

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 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 Whatsonindurham.net 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 Whatsonindurham.net 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

whatsonindurham.net

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