Tools & Wizards About Us
phatt.nz screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

phatt.nz

Weighintome

Page Load Speed

4.8 sec in total

First Response

530 ms

Resources Loaded

3.9 sec

Page Rendered

313 ms

phatt.nz screenshot

About Website

Welcome to phatt.nz homepage info - get ready to check Phatt best content right away, or after learning these important things about phatt.nz

Weighintome is a Weight loss and Mentoring site for Customers and Coaches.

Visit phatt.nz

Key Findings

We analyzed Phatt.nz page load time and found that the first response time was 530 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

phatt.nz performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.906

3/100

15%

TTI (Time to Interactive)

Value4.7 s

79/100

10%

Network Requests Diagram

phatt.nz

530 ms

phatt.nz

1028 ms

bootstrap.min.css

1074 ms

font-awesome.min.css

94 ms

owl.carousel.css

47 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Phatt.nz, 82% (28 requests) were made to Weighintome.b-cdn.net and 3% (1 request) were made to App.statuscake.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Weighintome.b-cdn.net.

Page Optimization Overview & Recommendations

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

Content Size

891.1 kB

After Optimization

830.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phatt.nz main page is 891.1 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. 40% of websites need less resources to load. Images take 743.6 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 56.0 kB

  • Original 62.1 kB
  • After minification 36.7 kB
  • After compression 6.1 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 25.4 kB, which is 41% 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 56.0 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 3.2 kB

  • Original 743.6 kB
  • After minification 740.5 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. Phatt images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 617 B

  • Original 53.4 kB
  • After minification 53.4 kB
  • After compression 52.8 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 1.1 kB

  • Original 32.0 kB
  • After minification 32.0 kB
  • After compression 30.9 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. Phatt.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (33%)

Requests Now

30

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phatt.nz

phatt.nz

530 ms

phatt.nz

phatt.nz

1028 ms

bootstrap.min.css

bootstrap.min.css

1074 ms

font-awesome.min.css

font-awesome.min.css

94 ms

owl.carousel.css

owl.carousel.css

47 ms

owl.theme.default.min.css

owl.theme.default.min.css

48 ms

templatemo-style2.css

templatemo-style2.css

780 ms

weighintome-logo.png

weighintome-logo.png

47 ms

index.php

index.php

776 ms

jquery.js

jquery.js

49 ms

bootstrap.min.js

bootstrap.min.js

48 ms

owl.carousel.min.js

owl.carousel.min.js

1036 ms

smoothscroll.js

smoothscroll.js

827 ms

custom-homepage.js

custom-homepage.js

51 ms

lazyload.min.js

lazyload.min.js

43 ms

lady-scales.jpg

lady-scales.jpg

53 ms

css

css

27 ms

Fitbit-background.jpg

Fitbit-background.jpg

85 ms

beach-yoga-background.jpg

beach-yoga-background.jpg

83 ms

woman-bed4.jpg

woman-bed4.jpg

6 ms

beach3.jpg

beach3.jpg

14 ms

running-shoes2.jpg

running-shoes2.jpg

5 ms

josie.jpeg

josie.jpeg

484 ms

sharon.jpeg

sharon.jpeg

600 ms

nikki.jpeg

nikki.jpeg

465 ms

vicki.jpeg

vicki.jpeg

711 ms

phattwithkat-logo.jpg

phattwithkat-logo.jpg

703 ms

Vera.jpeg

Vera.jpeg

726 ms

janine.jpeg

janine.jpeg

736 ms

gummer.jpeg

gummer.jpeg

1196 ms

alexis.jpg

alexis.jpg

872 ms

lisa.jpeg

lisa.jpeg

984 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf

20 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1181 ms

Accessibility Review

phatt.nz accessibility score

59

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

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

phatt.nz best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

phatt.nz SEO score

89

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

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

phatt.nz

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