Tools & Wizards About Us
qnary.es screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

qnary.es

Qnary - Executive Reputation Management and Talent Branding Solutions

Page Load Speed

2.5 sec in total

First Response

38 ms

Resources Loaded

2.1 sec

Page Rendered

351 ms

qnary.es screenshot

About Website

Click here to check amazing Qnary content. Otherwise, check out these important facts you probably never knew about qnary.es

Qnary is an award-winning executive reputation management and talent branding solutions company. By leveraging executives’ social media presence, Qnary helps establish and elevate their thought leader...

Visit qnary.es

Key Findings

We analyzed Qnary.es page load time and found that the first response time was 38 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

qnary.es performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value13.7 s

1/100

10%

TBT (Total Blocking Time)

Value3,880 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.183

66/100

15%

TTI (Time to Interactive)

Value32.8 s

0/100

10%

Network Requests Diagram

qnary.es

38 ms

www.qnary.com

29 ms

style.min.css

226 ms

plyr.css

222 ms

style.css

233 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Qnary.es, 42% (47 requests) were made to Qnary.com and 14% (16 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (943 ms) relates to the external source Qnary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.0 kB (3%)

Content Size

4.5 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qnary.es main page is 4.5 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. 75% 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.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 89.8 kB

  • Original 108.7 kB
  • After minification 105.1 kB
  • After compression 18.9 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 89.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 92 B

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

JavaScript Optimization

-17%

Potential reduce by 38.5 kB

  • Original 232.3 kB
  • After minification 232.2 kB
  • After compression 193.7 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 38.5 kB or 17% of the original size.

CSS Optimization

-10%

Potential reduce by 19.6 kB

  • Original 199.7 kB
  • After minification 199.7 kB
  • After compression 180.1 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. Qnary.es has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 63 (82%)

Requests Now

77

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qnary.es

qnary.es

38 ms

www.qnary.com

www.qnary.com

29 ms

style.min.css

style.min.css

226 ms

plyr.css

plyr.css

222 ms

style.css

style.css

233 ms

front-css.css

front-css.css

240 ms

new-flags.css

new-flags.css

234 ms

font-awesome.min.css

font-awesome.min.css

236 ms

grid-system.css

grid-system.css

278 ms

style.css

style.css

444 ms

header-secondary-nav.css

header-secondary-nav.css

291 ms

magnific.css

magnific.css

291 ms

css

css

54 ms

responsive.css

responsive.css

296 ms

ascend.css

ascend.css

294 ms

js_composer.min.css

js_composer.min.css

336 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

352 ms

css

css

76 ms

plyr.js

plyr.js

408 ms

front-js.js

front-js.js

352 ms

jquery.min.js

jquery.min.js

410 ms

jquery-migrate.min.js

jquery-migrate.min.js

392 ms

embed.min.js

embed.min.js

53 ms

3043.js

3043.js

55 ms

js

js

83 ms

js

js

131 ms

widget.js

widget.js

166 ms

css

css

74 ms

arrows_styles.css

arrows_styles.css

411 ms

animate.min.css

animate.min.css

410 ms

salient-social.js

salient-social.js

530 ms

jquery.easing.js

jquery.easing.js

530 ms

jquery.mousewheel.js

jquery.mousewheel.js

531 ms

priority.js

priority.js

531 ms

transit.js

transit.js

531 ms

waypoints.js

waypoints.js

683 ms

modernizr.js

modernizr.js

683 ms

imagesLoaded.min.js

imagesLoaded.min.js

683 ms

hoverintent.js

hoverintent.js

811 ms

magnific.js

magnific.js

810 ms

superfish.js

superfish.js

682 ms

init.js

init.js

943 ms

touchswipe.min.js

touchswipe.min.js

890 ms

vivus.min.js

vivus.min.js

891 ms

js_composer_front.min.js

js_composer_front.min.js

890 ms

30220.js

30220.js

718 ms

roundtrip.js

roundtrip.js

727 ms

wiv.js

wiv.js

726 ms

script

script

721 ms

Qnary-Logo.png

Qnary-Logo.png

354 ms

wsj.png

wsj.png

403 ms

cover-1.png

cover-1.png

783 ms

4.jpg

4.jpg

669 ms

static1.squarespace-2.png

static1.squarespace-2.png

721 ms

us.svg

us.svg

365 ms

es.svg

es.svg

457 ms

fr.svg

fr.svg

675 ms

pt.svg

pt.svg

676 ms

de.svg

de.svg

740 ms

cn.svg

cn.svg

741 ms

header-image.jpg

header-image.jpg

675 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

225 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

283 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

257 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

309 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

367 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

367 ms

5aU19_a8oxmIfNJdERySiA.ttf

5aU19_a8oxmIfNJdERySiA.ttf

351 ms

5aU69_a8oxmIdGl4AQ.ttf

5aU69_a8oxmIdGl4AQ.ttf

367 ms

5aU19_a8oxmIfLZcERySiA.ttf

5aU19_a8oxmIfLZcERySiA.ttf

317 ms

5aU19_a8oxmIfJpbERySiA.ttf

5aU19_a8oxmIfJpbERySiA.ttf

359 ms

5aU19_a8oxmIfMJaERySiA.ttf

5aU19_a8oxmIfMJaERySiA.ttf

367 ms

linea-basic-10.woff

linea-basic-10.woff

358 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

367 ms

linea-ecommerce-10.woff

linea-ecommerce-10.woff

426 ms

icomoon.woff

icomoon.woff

428 ms

bot.js

bot.js

156 ms

who.ashx

who.ashx

362 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

69 ms

TPFR2HSLPND7NDJIYQ76RV

TPFR2HSLPND7NDJIYQ76RV

12 ms

89 ms

fbevents.js

fbevents.js

26 ms

out

out

9 ms

sendrolling.js

sendrolling.js

8 ms

AP3QSYP7Q5CI3C7I7IUS4S

AP3QSYP7Q5CI3C7I7IUS4S

9 ms

out

out

14 ms

out

out

14 ms

out

out

16 ms

out

out

14 ms

out

out

14 ms

out

out

16 ms

out

out

46 ms

out

out

46 ms

out

out

48 ms

out

out

47 ms

out

out

48 ms

out

out

48 ms

trigger

trigger

51 ms

pixel

pixel

135 ms

tap.php

tap.php

126 ms

Pug

Pug

121 ms

xuid

xuid

13 ms

sd

sd

7 ms

sync

sync

20 ms

pixel

pixel

21 ms

rum

rum

20 ms

bounce

bounce

55 ms

in

in

3 ms

generic

generic

14 ms

generic

generic

3 ms

receive

receive

24 ms

core.js

core.js

307 ms

Accessibility Review

qnary.es 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.

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

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

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

qnary.es best practices score

83

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

qnary.es SEO score

93

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

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 Qnary.es 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 Qnary.es 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

qnary.es

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