Tools & Wizards About Us
pringle-thomas.co.nz screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

pringle-thomas.co.nz

Professional Psychotherapy, Psychotherapist, Psychotherapy Consultations, Mind-Body Therapy, Mindfulness Therapy, and Cognitive Therapy in Dunedin

Page Load Speed

2.4 sec in total

First Response

618 ms

Resources Loaded

1.5 sec

Page Rendered

223 ms

pringle-thomas.co.nz screenshot

About Website

Click here to check amazing Pringle Thomas content. Otherwise, check out these important facts you probably never knew about pringle-thomas.co.nz

Pauline Pringle provides professional psychotherapy, psychotherapist, psychotherapy consultations, mind-body therapy, mindfulness therapy, and cognitive therapy in Dunedin

Visit pringle-thomas.co.nz

Key Findings

We analyzed Pringle-thomas.co.nz page load time and found that the first response time was 618 ms and then it took 1.7 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

pringle-thomas.co.nz performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

pringle-thomas.co.nz

618 ms

pringle-thomas.nz

378 ms

grid.css

25 ms

style.css

117 ms

camera.css

192 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pringle-thomas.co.nz, 72% (36 requests) were made to Pringle-thomas.nz and 8% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (618 ms) belongs to the original domain Pringle-thomas.co.nz.

Page Optimization Overview & Recommendations

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

Content Size

553.7 kB

After Optimization

524.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pringle-thomas.co.nz main page is 553.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 366.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 12.9 kB

  • Original 16.4 kB
  • After minification 13.6 kB
  • After compression 3.5 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 2.8 kB, which is 17% 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 12.9 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 5.7 kB

  • Original 366.1 kB
  • After minification 360.3 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. Pringle Thomas images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 7.7 kB

  • Original 139.7 kB
  • After minification 139.5 kB
  • After compression 132.0 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

-10%

Potential reduce by 3.2 kB

  • Original 31.5 kB
  • After minification 31.5 kB
  • After compression 28.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. Pringle-thomas.co.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (67%)

Requests Now

45

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pringle-thomas.co.nz

pringle-thomas.co.nz

618 ms

pringle-thomas.nz

pringle-thomas.nz

378 ms

grid.css

grid.css

25 ms

style.css

style.css

117 ms

camera.css

camera.css

192 ms

owl-carousel.css

owl-carousel.css

97 ms

jquery.fancybox.css

jquery.fancybox.css

56 ms

contact-form.css

contact-form.css

187 ms

touchTouch.css

touchTouch.css

50 ms

jquery.js

jquery.js

94 ms

jquery-migrate.js

jquery-migrate.js

91 ms

device.min.js

device.min.js

143 ms

js

js

56 ms

script.js

script.js

124 ms

touchTouch.jquery.js

touchTouch.jquery.js

164 ms

animate.css

animate.css

65 ms

font-awesome.min.css

font-awesome.min.css

25 ms

sawmill.css

sawmill.css

36 ms

css

css

27 ms

css

css

34 ms

css

css

51 ms

embed

embed

202 ms

jquery.cookie.js

jquery.cookie.js

165 ms

jquery.easing.js

jquery.easing.js

24 ms

tmstickup.js

tmstickup.js

33 ms

jquery.ui.totop.js

jquery.ui.totop.js

142 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

95 ms

jquery.simplr.smoothscroll.min.js

jquery.simplr.smoothscroll.min.js

94 ms

superfish.js

superfish.js

93 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

94 ms

wow.js

wow.js

105 ms

pattern01.jpg

pattern01.jpg

126 ms

pringle-logo-1716464380.png

pringle-logo-1716464380.png

152 ms

banner-img-1716464446.jpg

banner-img-1716464446.jpg

197 ms

titbot.png

titbot.png

311 ms

ic-1-1716464897.png

ic-1-1716464897.png

291 ms

ic-2-1716464929.png

ic-2-1716464929.png

198 ms

ic-3-1716464957.png

ic-3-1716464957.png

192 ms

ic-4-1716464993.png

ic-4-1716464993.png

223 ms

1716464380.jpg

1716464380.jpg

253 ms

gal1-1716464503.jpg

gal1-1716464503.jpg

304 ms

gal2-1716464512.jpg

gal2-1716464512.jpg

234 ms

gal3-1716464524.jpg

gal3-1716464524.jpg

280 ms

mFT0WbgBwKPR_Z4hGN2qgx8D0A.ttf

mFT0WbgBwKPR_Z4hGN2qgx8D0A.ttf

19 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

11 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

26 ms

js

js

28 ms

search.js

search.js

4 ms

geometry.js

geometry.js

5 ms

main.js

main.js

10 ms

Accessibility Review

pringle-thomas.co.nz accessibility score

73

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

pringle-thomas.co.nz best practices score

58

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pringle-thomas.co.nz SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Pringle-thomas.co.nz 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 Pringle-thomas.co.nz 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

pringle-thomas.co.nz

Open Graph description is not detected on the main page of Pringle Thomas. 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: