Tools & Wizards About Us
highness.co screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

highness.co

Highness.co - A Branding & UX Design Driven Agency"

Page Load Speed

12 sec in total

First Response

20 ms

Resources Loaded

11.5 sec

Page Rendered

499 ms

highness.co screenshot

About Website

Welcome to highness.co homepage info - get ready to check Highness best content for Morocco right away, or after learning these important things about highness.co

A Branding and UX Agency designing and deploying solutions that delivers outstanding Customer Experiences.

Visit highness.co

Key Findings

We analyzed Highness.co page load time and found that the first response time was 20 ms and then it took 12 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

highness.co performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,440 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

highness.co

20 ms

highness.co

7159 ms

5ge2bmUYTqlpMNBCkIsYIKE2ZY4.js

29 ms

main.css

38 ms

email-decode.min.js

15 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 91% of them (62 requests) were addressed to the original Highness.co, 1% (1 request) were made to Ptimg.co and 1% (1 request) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (7.2 sec) belongs to the original domain Highness.co.

Page Optimization Overview & Recommendations

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

Content Size

917.8 kB

After Optimization

877.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Highness.co main page is 917.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 762.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 33.0 kB

  • Original 43.1 kB
  • After minification 43.0 kB
  • After compression 10.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 33.0 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 7.5 kB

  • Original 762.7 kB
  • After minification 755.2 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. Highness images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 20 B

  • Original 74.4 kB
  • After minification 74.4 kB
  • After compression 74.4 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 0 B

  • Original 37.6 kB
  • After minification 37.6 kB
  • After compression 37.6 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. Highness.co has all CSS files already compressed.

Requests Breakdown

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

Requests Now

59

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

highness.co

highness.co

20 ms

highness.co

highness.co

7159 ms

5ge2bmUYTqlpMNBCkIsYIKE2ZY4.js

5ge2bmUYTqlpMNBCkIsYIKE2ZY4.js

29 ms

main.css

main.css

38 ms

email-decode.min.js

email-decode.min.js

15 ms

svgxuse.js

svgxuse.js

252 ms

jquery.min.js

jquery.min.js

31 ms

bootstrap.min.js

bootstrap.min.js

27 ms

base.js

base.js

62 ms

waypoints.min.js

waypoints.min.js

30 ms

jquery.validate.js

jquery.validate.js

62 ms

owl.carousel.js

owl.carousel.js

63 ms

froogaloop2.min.js

froogaloop2.min.js

13 ms

wow.js

wow.js

59 ms

main.js

main.js

60 ms

-M_nxpXUJDH_gh_u6X3_Hmze1WI.js

-M_nxpXUJDH_gh_u6X3_Hmze1WI.js

38 ms

gtm.js

gtm.js

82 ms

180421931

180421931

213 ms

logo-highness-black.svg

logo-highness-black.svg

26 ms

play-icon.svg

play-icon.svg

25 ms

strategy-icon.svg

strategy-icon.svg

27 ms

design-icon.svg

design-icon.svg

18 ms

production-icon.svg

production-icon.svg

26 ms

move.png

move.png

18 ms

apple.png

apple.png

29 ms

greenscreenanimals.png

greenscreenanimals.png

29 ms

uthermic.png

uthermic.png

36 ms

avi.png

avi.png

37 ms

db.png

db.png

35 ms

canva.png

canva.png

35 ms

du.png

du.png

39 ms

zerotxt.png

zerotxt.png

40 ms

redbull.png

redbull.png

45 ms

hoop.png

hoop.png

46 ms

sunwarrior.png

sunwarrior.png

47 ms

videolan.png

videolan.png

48 ms

ted.png

ted.png

50 ms

emirates.png

emirates.png

54 ms

huffingtonpost.png

huffingtonpost.png

56 ms

eskanbank.png

eskanbank.png

57 ms

composingcommunity.png

composingcommunity.png

58 ms

globotech.png

globotech.png

56 ms

persil.png

persil.png

60 ms

sunwarrior-highness.jpg

sunwarrior-highness.jpg

66 ms

sunwarrior.png

sunwarrior.png

2003 ms

apple-highness.jpg

apple-highness.jpg

83 ms

apple.png

apple.png

1884 ms

zerotxt-highness.jpg

zerotxt-highness.jpg

83 ms

zerotxt.png

zerotxt.png

3881 ms

du-highness.jpg

du-highness.jpg

81 ms

du.png

du.png

3880 ms

facebook-icon.svg

facebook-icon.svg

82 ms

twitter-icon.svg

twitter-icon.svg

88 ms

piwik.js

piwik.js

8 ms

linkedin-icon.svg

linkedin-icon.svg

91 ms

instagram-icon.svg

instagram-icon.svg

184 ms

medium-icon.svg

medium-icon.svg

183 ms

dribbble-icon.svg

dribbble-icon.svg

179 ms

facebook-icon.svg

facebook-icon.svg

31 ms

twitter-icon.svg

twitter-icon.svg

27 ms

linkedin-icon.svg

linkedin-icon.svg

31 ms

instagram-icon.svg

instagram-icon.svg

31 ms

medium-icon.svg

medium-icon.svg

34 ms

dribbble-icon.svg

dribbble-icon.svg

35 ms

hinted-FFMetaSerifPro-Light.woff

hinted-FFMetaSerifPro-Light.woff

4005 ms

hinted-Geogrotesque-Bold.woff

hinted-Geogrotesque-Bold.woff

3766 ms

hinted-Geogrotesque-SemiBold.woff

hinted-Geogrotesque-SemiBold.woff

2478 ms

api.js

api.js

11 ms

Accessibility Review

highness.co accessibility score

62

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

<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

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

highness.co 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

highness.co SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Highness.co 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 Highness.co 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

highness.co

Open Graph description is not detected on the main page of Highness. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: