Report Summary

  • 17

    Performance

    Renders faster than
    33% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

vapor.bg

Вейп Модове | Вейп Течности | Вейп Магазин | VAPOR.BG

Page Load Speed

33.3 sec in total

First Response

582 ms

Resources Loaded

11.8 sec

Page Rendered

20.9 sec

vapor.bg screenshot

About Website

Click here to check amazing VAPOR content. Otherwise, check out these important facts you probably never knew about vapor.bg

Вейп устройства, Вейп Модове, Вейп Течности, Вейп Изпарители, Вейп наргиле, Електронни цигари, Никотинови и Безникотинови течности, Вейпове | VAPOR.BG

Visit vapor.bg

Key Findings

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

Performance Metrics

vapor.bg performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value4,400 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.081

94/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

vapor.bg

582 ms

www.vapor.bg

795 ms

7qd4r.css

403 ms

7r14i.css

280 ms

4oah.css

309 ms

Our browser made a total of 272 requests to load all elements on the main page. We found that 14% of them (37 requests) were addressed to the original Vapor.bg, 24% (65 requests) were made to I0.wp.com and 19% (51 requests) were made to I1.wp.com. The less responsive or slowest element that took the longest time to load (7 sec) relates to the external source I1.wp.com.

Page Optimization Overview & Recommendations

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

Content Size

10.8 MB

After Optimization

10.2 MB

In fact, the total size of Vapor.bg main page is 10.8 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. Only a small number of websites need less resources to load. Images take 10.0 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 585.4 kB

  • Original 650.4 kB
  • After minification 646.3 kB
  • After compression 65.0 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 585.4 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 132 B

  • Original 10.0 MB
  • After minification 10.0 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. VAPOR images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 3.4 kB

  • Original 134.2 kB
  • After minification 134.2 kB
  • After compression 130.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

-1%

Potential reduce by 1.1 kB

  • Original 78.5 kB
  • After minification 78.5 kB
  • After compression 77.5 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. Vapor.bg has all CSS files already compressed.

Requests Breakdown

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

Requests Now

244

After Optimization

204

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

Accessibility Review

vapor.bg accessibility score

85

Accessibility Issues

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

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

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

vapor.bg best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

vapor.bg SEO score

92

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

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

    BG

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vapor.bg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Bulgarian language. Our system also found out that Vapor.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 VAPOR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: