Tools & Wizards About Us
qoovee.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

qoovee.com

B2B marketplace | Wholesale suppliers and buyers of products and services on Qoovee

Page Load Speed

2.3 sec in total

First Response

183 ms

Resources Loaded

1.4 sec

Page Rendered

736 ms

qoovee.com screenshot

About Website

Visit qoovee.com now to see the best up-to-date Qoovee content for Turkey and also check out these interesting facts you probably never knew about qoovee.com

Qoovee B2B Marketplace helps to make profitable deals for buyers and suppliers, small and medium-sized businesses from China, Turkey, India, UAE and the CIS countries.

Visit qoovee.com

Key Findings

We analyzed Qoovee.com page load time and found that the first response time was 183 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

qoovee.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value760 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

qoovee.com

183 ms

234 ms

home.css

116 ms

bundle.css

41 ms

hijack-styles.css

27 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 95% of them (52 requests) were addressed to the original Qoovee.com, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Rec.smartlook.com. The less responsive or slowest element that took the longest time to load (429 ms) belongs to the original domain Qoovee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.0 kB (4%)

Content Size

1.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qoovee.com 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. 70% of websites need less resources to load. Images take 852.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 38.8 kB

  • Original 49.1 kB
  • After minification 49.1 kB
  • After compression 10.3 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 38.8 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 934 B

  • Original 852.8 kB
  • After minification 851.8 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. Qoovee images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 304 B

  • Original 190.2 kB
  • After minification 190.2 kB
  • After compression 189.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 11 B

  • Original 48.5 kB
  • After minification 48.5 kB
  • After compression 48.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. Qoovee.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

43

After Optimization

33

  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qoovee. 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 as a result speed up the page load time.

Network Requests Diagram

qoovee.com

qoovee.com

183 ms

234 ms

home.css

home.css

116 ms

bundle.css

bundle.css

41 ms

hijack-styles.css

hijack-styles.css

27 ms

180 ms

vendor.js

vendor.js

55 ms

home.js

home.js

179 ms

gtm.js

gtm.js

272 ms

recorder.js

recorder.js

271 ms

fbevents.js

fbevents.js

270 ms

triangle.svg

triangle.svg

220 ms

icon-profile-white.svg

icon-profile-white.svg

217 ms

RU.svg

RU.svg

222 ms

US.svg

US.svg

220 ms

TR.svg

TR.svg

218 ms

AE.svg

AE.svg

223 ms

CN.svg

CN.svg

275 ms

DE.svg

DE.svg

276 ms

logo.svg

logo.svg

275 ms

icon-menu-search-white.svg

icon-menu-search-white.svg

272 ms

icon-search.svg

icon-search.svg

273 ms

icon-shield.svg

icon-shield.svg

270 ms

icon-box.svg

icon-box.svg

277 ms

icon-eye.svg

icon-eye.svg

278 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8.png

281 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_2.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_2.png

281 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_7.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_7.png

279 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_8.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_8.png

280 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_10.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_10.png

278 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_11.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_11.png

283 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_12.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_12.png

281 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_22.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_22.png

281 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_23.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_23.png

283 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_24.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_24.png

283 ms

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_27_gBxV5fD.png

%D0%BA%D0%B0%D1%80%D1%82%D0%B8%D0%BD%D0%BA%D0%B8_%D0%B4%D0%BB%D1%8F_%D0%BA%D0%B0%D1%82%D0%B5%D0%B3%D0%BE%D1%80%D0%B8%D0%B8_27_gBxV5fD.png

285 ms

video-poster.jpg

video-poster.jpg

293 ms

icon-appstore-new.svg

icon-appstore-new.svg

284 ms

iphone-12--blue.svg

iphone-12--blue.svg

302 ms

footer_mastercard.svg

footer_mastercard.svg

409 ms

footer_visa.svg

footer_visa.svg

287 ms

jivosite.svg

jivosite.svg

285 ms

logo-gray.svg

logo-gray.svg

408 ms

google.svg

google.svg

295 ms

Lato-Regular.woff

Lato-Regular.woff

408 ms

Lato-Medium.woff

Lato-Medium.woff

426 ms

Lato-Light.woff

Lato-Light.woff

247 ms

Lato-Semibold.woff

Lato-Semibold.woff

196 ms

Lato-Bold.woff

Lato-Bold.woff

242 ms

Lato-Black.woff

Lato-Black.woff

194 ms

Lato-Heavy.woff

Lato-Heavy.woff

429 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

285 ms

themify.woff

themify.woff

237 ms

qv-icons.woff

qv-icons.woff

190 ms

linkedin.svg

linkedin.svg

190 ms

Accessibility Review

qoovee.com accessibility score

60

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

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

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

qoovee.com 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

Missing source maps for large first-party JavaScript

SEO Factors

qoovee.com SEO score

88

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qoovee.com 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 Qoovee.com 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

qoovee.com

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