Tools & Wizards About Us
buddywatch.app screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

buddywatch.app

Your Apple Watch stylist • buddywatch • Amazing watch faces

Page Load Speed

6.5 sec in total

First Response

2.6 sec

Resources Loaded

3.6 sec

Page Rendered

272 ms

buddywatch.app screenshot

About Website

Click here to check amazing Buddy Watch content. Otherwise, check out these important facts you probably never knew about buddywatch.app

Discover your personal Apple Watch stylist. Find and download the perfect watch faces for your Apple Watch. Anytime. Anywhere

Visit buddywatch.app

Key Findings

We analyzed Buddywatch.app page load time and found that the first response time was 2.6 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

buddywatch.app performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

buddywatch.app

2638 ms

js

68 ms

adsbygoogle.js

165 ms

email-decode.min.js

8 ms

track.js

323 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 25% of them (9 requests) were addressed to the original Buddywatch.app, 17% (6 requests) were made to Fonts.gstatic.com and 11% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Buddywatch.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 330.3 kB (29%)

Content Size

1.1 MB

After Optimization

795.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Buddywatch.app main page is 1.1 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. 40% of websites need less resources to load. HTML takes 381.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 313.6 kB

  • Original 381.0 kB
  • After minification 380.9 kB
  • After compression 67.4 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 313.6 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 16.2 kB

  • Original 370.8 kB
  • After minification 354.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. Buddy Watch images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 443 B

  • Original 367.0 kB
  • After minification 367.0 kB
  • After compression 366.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 14 B

  • Original 6.9 kB
  • After minification 6.9 kB
  • After compression 6.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. Buddywatch.app has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (57%)

Requests Now

28

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

buddywatch.app

buddywatch.app

2638 ms

js

js

68 ms

adsbygoogle.js

adsbygoogle.js

165 ms

email-decode.min.js

email-decode.min.js

8 ms

track.js

track.js

323 ms

fontawesome.min.css

fontawesome.min.css

287 ms

jquery.js

jquery.js

535 ms

OneSignalSDK.js

OneSignalSDK.js

164 ms

firebase-app.js

firebase-app.js

38 ms

firebase-analytics.js

firebase-analytics.js

40 ms

e-202410.js

e-202410.js

36 ms

autoptimize_a89e862074ab0621ada398bfdeb7308f.js

autoptimize_a89e862074ab0621ada398bfdeb7308f.js

35 ms

analytics.js

analytics.js

112 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

299 ms

fbevents.js

fbevents.js

111 ms

label-co2-website-white-en.png

label-co2-website-white-en.png

364 ms

Sea-Salt-Love-800x710-1.png

Sea-Salt-Love-800x710-1.png

699 ms

show_ads_impl.js

show_ads_impl.js

389 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

51 ms

linkid.js

linkid.js

7 ms

collect

collect

33 ms

collect

collect

27 ms

collect

collect

22 ms

ga-audiences

ga-audiences

27 ms

6057976520f2c

6057976520f2c

330 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

301 ms

css

css

68 ms

main.js

main.js

28 ms

ads

ads

62 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3ig.ttf

56 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3ig.ttf

57 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3ig.ttf

127 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMhhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMhhKg.ttf

135 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMhhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMhhKg.ttf

136 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMhhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMhhKg.ttf

135 ms

ca-pub-9846034826662081

ca-pub-9846034826662081

167 ms

Accessibility Review

buddywatch.app accessibility score

73

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

[aria-*] attributes do not match their roles

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.

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

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

buddywatch.app 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

High

Page has valid source maps

SEO Factors

buddywatch.app SEO score

86

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

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 Buddywatch.app 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 Buddywatch.app 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

buddywatch.app

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