Tools & Wizards About Us
witneygazette.net screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

witneygazette.net

Witney news, sport and information from the Witney Gazette and its sister titles

Page Load Speed

3.9 sec in total

First Response

193 ms

Resources Loaded

2.9 sec

Page Rendered

744 ms

witneygazette.net screenshot

About Website

Click here to check amazing Witney Gazette content. Otherwise, check out these important facts you probably never knew about witneygazette.net

Witney and Oxfordshire news coverage from the Witney Gazette. Comprehensive local Witney news stories and headlines with regular updates

Visit witneygazette.net

Key Findings

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

Performance Metrics

witneygazette.net performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value3,850 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.168

71/100

15%

TTI (Time to Interactive)

Value39.3 s

0/100

10%

Network Requests Diagram

witneygazette.net

193 ms

www.witneygazette.co.uk

777 ms

css

43 ms

css2

61 ms

palette-7-sans-serif-vars.css

154 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Witneygazette.net, 66% (88 requests) were made to Witneygazette.co.uk and 4% (5 requests) were made to Api.iconify.design. The less responsive or slowest element that took the longest time to load (830 ms) relates to the external source Witneygazette.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 324.3 kB (21%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Witneygazette.net main page is 1.5 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. 70% of websites need less resources to load. Javascripts take 623.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 260.2 kB

  • Original 323.0 kB
  • After minification 279.1 kB
  • After compression 62.8 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 43.9 kB, which is 14% 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 260.2 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 16.5 kB

  • Original 549.7 kB
  • After minification 533.2 kB

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. Witney Gazette images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 47.5 kB

  • Original 623.1 kB
  • After minification 619.1 kB
  • After compression 575.6 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

-0%

Potential reduce by 149 B

  • Original 41.8 kB
  • After minification 41.8 kB
  • After compression 41.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. Witneygazette.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (32%)

Requests Now

129

After Optimization

88

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

witneygazette.net

witneygazette.net

193 ms

www.witneygazette.co.uk

www.witneygazette.co.uk

777 ms

css

css

43 ms

css2

css2

61 ms

palette-7-sans-serif-vars.css

palette-7-sans-serif-vars.css

154 ms

header-footer.css

header-footer.css

300 ms

blockhomepage.css

blockhomepage.css

309 ms

jquery.min.js

jquery.min.js

38 ms

376 ms

wrapperMessagingWithoutDetection.js

wrapperMessagingWithoutDetection.js

47 ms

launch-98090dfa3d73.min.js

launch-98090dfa3d73.min.js

43 ms

cmp_shim.js

cmp_shim.js

36 ms

lt.min.js

lt.min.js

37 ms

sync.min.js

sync.min.js

38 ms

8199811887536872459

8199811887536872459

17 ms

iconify.min.js

iconify.min.js

37 ms

evvnt_discovery_plugin-latest.min.js

evvnt_discovery_plugin-latest.min.js

30 ms

widgets.js

widgets.js

29 ms

global.js

global.js

300 ms

homepage.js

homepage.js

153 ms

newsletters.js

newsletters.js

421 ms

260 ms

VisitorAPI.js

VisitorAPI.js

300 ms

omniture.js

omniture.js

298 ms

all.js

all.js

25 ms

embed.js

embed.js

58 ms

embed_v1.0.12.js

embed_v1.0.12.js

51 ms

advertising.js

advertising.js

195 ms

apstag.js

apstag.js

120 ms

170 ms

18482718.jpg

18482718.jpg

169 ms

18480923.jpg

18480923.jpg

168 ms

18480923.jpg

18480923.jpg

169 ms

18481088.jpg

18481088.jpg

167 ms

18481088.jpg

18481088.jpg

168 ms

17563066.jpg

17563066.jpg

231 ms

17563066.jpg

17563066.jpg

230 ms

18481688.jpg

18481688.jpg

230 ms

18481688.jpg

18481688.jpg

231 ms

18259934.jpg

18259934.jpg

230 ms

18259934.jpg

18259934.jpg

229 ms

16649192.jpg

16649192.jpg

297 ms

16649192.jpg

16649192.jpg

296 ms

18480206.jpg

18480206.jpg

382 ms

18480206.jpg

18480206.jpg

298 ms

18477463.jpg

18477463.jpg

297 ms

18477463.jpg

18477463.jpg

298 ms

18001147.jpg

18001147.jpg

366 ms

18001147.jpg

18001147.jpg

369 ms

18063666.jpg

18063666.jpg

368 ms

18063666.jpg

18063666.jpg

370 ms

18476539.jpg

18476539.jpg

525 ms

18476539.jpg

18476539.jpg

441 ms

18478661.jpg

18478661.jpg

443 ms

18478661.jpg

18478661.jpg

442 ms

16552521.jpg

16552521.jpg

444 ms

16552521.jpg

16552521.jpg

454 ms

18476090.jpg

18476090.jpg

685 ms

18476090.jpg

18476090.jpg

516 ms

18476701.jpg

18476701.jpg

643 ms

18476701.jpg

18476701.jpg

518 ms

17003182.jpg

17003182.jpg

682 ms

17003182.jpg

17003182.jpg

593 ms

id

id

127 ms

AppMeasurement.min.js

AppMeasurement.min.js

54 ms

data

data

171 ms

18483260.jpg

18483260.jpg

538 ms

18483420.jpg

18483420.jpg

513 ms

all.js

all.js

24 ms

RC2f293f723ed74d1cab1ae093825aefd0-source.min.js

RC2f293f723ed74d1cab1ae093825aefd0-source.min.js

56 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

52 ms

dest5.html

dest5.html

85 ms

18483420.jpg

18483420.jpg

506 ms

18480233.jpg

18480233.jpg

670 ms

18480233.jpg

18480233.jpg

509 ms

18199402.jpg

18199402.jpg

734 ms

18199402.jpg

18199402.jpg

579 ms

18479914.jpg

18479914.jpg

714 ms

akar-icons.js

akar-icons.js

103 ms

eva.js

eva.js

112 ms

fe.js

fe.js

120 ms

ion.js

ion.js

130 ms

ooui.js

ooui.js

130 ms

settings

settings

98 ms

embed_lib_v1.0.12.css

embed_lib_v1.0.12.css

18 ms

embed_lib_v1.0.12.js

embed_lib_v1.0.12.js

31 ms

lt.iframe.html

lt.iframe.html

21 ms

18479914.jpg

18479914.jpg

530 ms

18483697.jpg

18483697.jpg

534 ms

18483697.jpg

18483697.jpg

593 ms

18483694.jpg

18483694.jpg

605 ms

18483694.jpg

18483694.jpg

607 ms

ibs:dpid=411&dpuuid=ZtFfkgAAAMfazgN2

ibs:dpid=411&dpuuid=ZtFfkgAAAMfazgN2

22 ms

18483692.jpg

18483692.jpg

660 ms

pixels

pixels

5 ms

pixel

pixel

45 ms

utsync.ashx

utsync.ashx

56 ms

382416.gif

382416.gif

75 ms

lotame

lotame

79 ms

5907

5907

121 ms

g.json

g.json

32 ms

beacon.js

beacon.js

13 ms

18483692.jpg

18483692.jpg

612 ms

18483687.jpg

18483687.jpg

764 ms

18483687.jpg

18483687.jpg

615 ms

18475124.jpg

18475124.jpg

795 ms

18475124.jpg

18475124.jpg

673 ms

pixel

pixel

13 ms

18483681.jpg

18483681.jpg

609 ms

18483681.jpg

18483681.jpg

614 ms

18475150.jpg

18475150.jpg

775 ms

18475150.jpg

18475150.jpg

675 ms

18476669.jpg

18476669.jpg

669 ms

7456581.jpg

7456581.jpg

614 ms

18476539.jpg

18476539.jpg

679 ms

18483682.jpg

18483682.jpg

682 ms

18483682.jpg

18483682.jpg

688 ms

18483696.jpg

18483696.jpg

830 ms

18483696.jpg

18483696.jpg

651 ms

18483684.jpg

18483684.jpg

675 ms

18483684.jpg

18483684.jpg

676 ms

18483653.jpg

18483653.jpg

612 ms

18483653.jpg

18483653.jpg

625 ms

18483645.jpg

18483645.jpg

645 ms

18483645.jpg

18483645.jpg

627 ms

18483646.jpg

18483646.jpg

605 ms

18483646.jpg

18483646.jpg

608 ms

18483647.jpg

18483647.jpg

612 ms

18483647.jpg

18483647.jpg

633 ms

ipso-regulated.svg

ipso-regulated.svg

600 ms

love-local.png

love-local.png

668 ms

595 ms

optimus_rules.json

optimus_rules.json

10 ms

Accessibility Review

witneygazette.net accessibility score

70

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Page has valid source maps

SEO Factors

witneygazette.net SEO score

84

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

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

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

witneygazette.net

Open Graph description is not detected on the main page of Witney Gazette. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: