Tools & Wizards About Us
buddywatch.app screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    28% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

buddywatch.app

Your Apple Watch stylist • buddywatch • Amazing watch faces

Page Load Speed

7.8 sec in total

First Response

1.3 sec

Resources Loaded

5.6 sec

Page Rendered

953 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 1.3 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

buddywatch.app performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value29.7 s

0/100

10%

TBT (Total Blocking Time)

Value44,810 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value58.9 s

0/100

10%

Network Requests Diagram

buddywatch.app

1255 ms

js

164 ms

adsbygoogle.js

654 ms

email-decode.min.js

73 ms

track.js

1028 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 22% of them (17 requests) were addressed to the original Buddywatch.app, 11% (8 requests) were made to Fonts.gstatic.com and 8% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Buddywatch.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 344.3 kB (13%)

Content Size

2.7 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Buddywatch.app 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 316.9 kB

  • Original 385.0 kB
  • After minification 385.0 kB
  • After compression 68.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. 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 316.9 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 18.9 kB

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

JavaScript Optimization

-11%

Potential reduce by 8.5 kB

  • Original 74.3 kB
  • After minification 74.3 kB
  • After compression 65.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 8.5 kB or 11% of the original size.

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 40 (63%)

Requests Now

64

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 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 31 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

buddywatch.app

buddywatch.app

1255 ms

js

js

164 ms

adsbygoogle.js

adsbygoogle.js

654 ms

email-decode.min.js

email-decode.min.js

73 ms

track.js

track.js

1028 ms

fontawesome.min.css

fontawesome.min.css

787 ms

jquery.js

jquery.js

747 ms

OneSignalSDK.js

OneSignalSDK.js

799 ms

firebase-app.js

firebase-app.js

788 ms

firebase-analytics.js

firebase-analytics.js

794 ms

e-202241.js

e-202241.js

788 ms

autoptimize_f9dee1cbef4b603b7de1dd36b054f5ed.js

autoptimize_f9dee1cbef4b603b7de1dd36b054f5ed.js

104 ms

analytics.js

analytics.js

607 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

537 ms

fbevents.js

fbevents.js

410 ms

label-co2-website-white-en.png

label-co2-website-white-en.png

576 ms

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

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

595 ms

show_ads_impl.js

show_ads_impl.js

320 ms

zrt_lookup.html

zrt_lookup.html

165 ms

identity.js

identity.js

58 ms

1415337908817137

1415337908817137

178 ms

linkid.js

linkid.js

46 ms

collect

collect

134 ms

collect

collect

81 ms

collect

collect

326 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

506 ms

invisible.js

invisible.js

62 ms

ga-audiences

ga-audiences

266 ms

css

css

259 ms

cookie.js

cookie.js

278 ms

integrator.js

integrator.js

250 ms

ads

ads

287 ms

75b1a5d61f91591a

75b1a5d61f91591a

63 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3ig.ttf

196 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3ig.ttf

340 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3ig.ttf

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3ig.ttf

428 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMhhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMhhKg.ttf

428 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMhhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMhhKg.ttf

429 ms

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMhhKg.ttf

Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMhhKg.ttf

426 ms

integrator.js

integrator.js

303 ms

ads

ads

931 ms

5bbe539ad7c95ad1b7dc2874c2ab6f46.js

5bbe539ad7c95ad1b7dc2874c2ab6f46.js

27 ms

load_preloaded_resource.js

load_preloaded_resource.js

163 ms

2c31c29323708f8c18cb525f4f35abd1.js

2c31c29323708f8c18cb525f4f35abd1.js

104 ms

abg_lite.js

abg_lite.js

182 ms

window_focus.js

window_focus.js

180 ms

qs_click_protection.js

qs_click_protection.js

150 ms

rx_lidar.js

rx_lidar.js

210 ms

fac60d4cdc0b8be56d9f8d6f9ac54a3d.js

fac60d4cdc0b8be56d9f8d6f9ac54a3d.js

87 ms

icon.png

icon.png

118 ms

s

s

295 ms

cookie_push_onload.html

cookie_push_onload.html

272 ms

dpixel

dpixel

267 ms

css

css

95 ms

iubenda.js

iubenda.js

721 ms

Hello-Spring-800x710-1.png

Hello-Spring-800x710-1.png

405 ms

sodar

sodar

169 ms

Kaleido-Sunset-800x710-1.png

Kaleido-Sunset-800x710-1.png

404 ms

Tiles-500x500-1.png

Tiles-500x500-1.png

372 ms

Flip-Date-500x500-1.png

Flip-Date-500x500-1.png

140 ms

Bubbles-500x500-1.png

Bubbles-500x500-1.png

294 ms

Purple-Waves-500x500-1.png

Purple-Waves-500x500-1.png

415 ms

Dark-Space-800x710-1.png

Dark-Space-800x710-1.png

435 ms

activeview

activeview

293 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

51 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

51 ms

7JEUJG1jVChIMuhiOxVurQN9pIQLeBNKr_aiZz5iC5Y.js

7JEUJG1jVChIMuhiOxVurQN9pIQLeBNKr_aiZz5iC5Y.js

133 ms

pixel

pixel

251 ms

pixel

pixel

251 ms

pixel

pixel

250 ms

sodar2.js

sodar2.js

169 ms

pixel

pixel

69 ms

pixel

pixel

102 ms

runner.html

runner.html

57 ms

aframe

aframe

83 ms

pixel

pixel

62 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

75

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

Browser errors were logged to the console

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: