Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

smartwatch.bg

Smartwatch.bg - Умни часовници

Page Load Speed

16 sec in total

First Response

4.3 sec

Resources Loaded

11 sec

Page Rendered

617 ms

About Website

Click here to check amazing Smartwatch content for Bulgaria. Otherwise, check out these important facts you probably never knew about smartwatch.bg

smart watch, smart watch, смартуоч, смарт уоч, умни часовници, умни гривни, smartband, smart band, apple watch,pebble, fitbit, garmin, jawbone, motorola, asus, lg

Visit smartwatch.bg

Key Findings

We analyzed Smartwatch.bg page load time and found that the first response time was 4.3 sec and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

smartwatch.bg performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

7/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

smartwatch.bg

4342 ms

products-application-f89722dc5ef96a452fdec5bcb37d4f3c4a1fdc604231e1363bdb18786ddfa0b5.css

46 ms

products-application-cd6a0116a258c64723c2452a19650bdba8989e2a48c03d5479ea8d3e443cd717.js

29 ms

home-eb2d7381d4011ed21ffdbbe8964c355c39be67eb2a7d95b2b5d3defee30cb708.js

26 ms

products-common-62dc02178dc98c6cd8cee2153d4616c35ec3d25c16739790d1bfbd715aa249e2.js

30 ms

Our browser made a total of 175 requests to load all elements on the main page. We found that 99% of them (173 requests) were addressed to the original Smartwatch.bg, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Laptop.bg. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Smartwatch.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 458.6 kB (12%)

Content Size

3.7 MB

After Optimization

3.3 MB

In fact, the total size of Smartwatch.bg main page is 3.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 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 284.6 kB

  • Original 315.0 kB
  • After minification 313.8 kB
  • After compression 30.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 284.6 kB or 90% of the original size.

Image Optimization

-5%

Potential reduce by 162.0 kB

  • Original 3.3 MB
  • After minification 3.1 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. Smartwatch images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 10.0 kB

  • Original 70.9 kB
  • After minification 70.9 kB
  • After compression 60.9 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 10.0 kB or 14% of the original size.

CSS Optimization

-2%

Potential reduce by 2.0 kB

  • Original 89.7 kB
  • After minification 89.7 kB
  • After compression 87.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. Smartwatch.bg has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (7%)

Requests Now

169

After Optimization

157

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

Accessibility Review

smartwatch.bg accessibility score

75

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-hidden="true"] elements contain focusable descendents

High

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

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

smartwatch.bg 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

smartwatch.bg SEO score

98

Search Engine Optimization Advices

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

    BG

  • Language Claimed

    BG

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smartwatch.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Smartwatch.bg 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

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