Tools & Wizards About Us
kapany.net screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

kapany.net

Edgeuno

Page Load Speed

1.7 sec in total

First Response

14 ms

Resources Loaded

713 ms

Page Rendered

941 ms

kapany.net screenshot

About Website

Visit kapany.net now to see the best up-to-date Kapany content and also check out these interesting facts you probably never knew about kapany.net

Experience the incredible speed and expansion of our Edge Network in Latin America. Join the fastest growing Edge Network in Latin America.

Visit kapany.net

Key Findings

We analyzed Kapany.net page load time and found that the first response time was 14 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

kapany.net performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

kapany.net

14 ms

edgeuno.com

200 ms

style.min.css

49 ms

menu-image.css

61 ms

svgs-attachment.css

62 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kapany.net, 65% (50 requests) were made to Webedgeuno.cachefly.net and 29% (22 requests) were made to Edgeuno.com. The less responsive or slowest element that took the longest time to load (383 ms) relates to the external source Salesiq.zohopublic.com.

Page Optimization Overview & Recommendations

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

Content Size

2.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kapany.net main page is 2.2 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 101.9 kB

  • Original 121.3 kB
  • After minification 97.5 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 23.8 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 101.9 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 15.3 kB

  • Original 2.0 MB
  • After minification 2.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. Kapany images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 360 B

  • Original 51.0 kB
  • After minification 51.0 kB
  • After compression 50.6 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 403 B

  • Original 54.3 kB
  • After minification 54.3 kB
  • After compression 53.9 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. Kapany.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (39%)

Requests Now

72

After Optimization

44

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kapany.net

kapany.net

14 ms

edgeuno.com

edgeuno.com

200 ms

style.min.css

style.min.css

49 ms

menu-image.css

menu-image.css

61 ms

svgs-attachment.css

svgs-attachment.css

62 ms

front-css.css

front-css.css

59 ms

bootstrap.min.css

bootstrap.min.css

52 ms

owl.carousel.min.css

owl.carousel.min.css

60 ms

owl.theme.default.min.css

owl.theme.default.min.css

61 ms

style-v4.min.css

style-v4.min.css

62 ms

header-style-v2-3.min.css

header-style-v2-3.min.css

62 ms

jquery.min.js

jquery.min.js

44 ms

front-js.js

front-js.js

77 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

46 ms

owl.carousel.min.js

owl.carousel.min.js

76 ms

js

js

289 ms

contact.js

contact.js

27 ms

principal.min.js

principal.min.js

101 ms

lazyload.min.js

lazyload.min.js

109 ms

wgarrowdown.png

wgarrowdown.png

160 ms

blue-box-bg.svg

blue-box-bg.svg

164 ms

flash-icon.png

flash-icon.png

160 ms

cache-icon.png

cache-icon.png

160 ms

noip-icon.png

noip-icon.png

162 ms

footer-box-bg.svg

footer-box-bg.svg

161 ms

nav-dropdown.svg

nav-dropdown.svg

167 ms

widget

widget

383 ms

Figtree-Regular.ttf

Figtree-Regular.ttf

159 ms

Figtree-Light.ttf

Figtree-Light.ttf

159 ms

Figtree-ExtraBold.ttf

Figtree-ExtraBold.ttf

159 ms

logo-main.svg

logo-main.svg

48 ms

Bare-metal-server.svg

Bare-metal-server.svg

22 ms

database-point.svg

database-point.svg

12 ms

menu-cloud-apps.svg

menu-cloud-apps.svg

7 ms

public-cloud.svg

public-cloud.svg

10 ms

menu-sap.svg

menu-sap.svg

8 ms

menu-cloud-private.svg

menu-cloud-private.svg

11 ms

IP-Transit.svg

IP-Transit.svg

13 ms

Dark-fiber.svg

Dark-fiber.svg

15 ms

Ethernet.svg

Ethernet.svg

17 ms

menu-vpn.svg

menu-vpn.svg

14 ms

hero-figure.webp

hero-figure.webp

18 ms

cloud.svg

cloud.svg

16 ms

network-solutions.webp

network-solutions.webp

19 ms

edge-solutions.webp

edge-solutions.webp

20 ms

no-ip.webp

no-ip.webp

21 ms

cachefly.png

cachefly.png

20 ms

flashstart.png

flashstart.png

20 ms

noip-container.webp

noip-container.webp

22 ms

cachefly-container.webp

cachefly-container.webp

21 ms

flashstar-container.webp

flashstar-container.webp

24 ms

deploy.webp

deploy.webp

25 ms

view-cartagena-de-indias-colombia-1-scaled.jpg

view-cartagena-de-indias-colombia-1-scaled.jpg

29 ms

Quito.jpeg

Quito.jpeg

26 ms

connectivity-info.svg

connectivity-info.svg

24 ms

EN-white-map-1.jpg

EN-white-map-1.jpg

26 ms

The-Team.webp

The-Team.webp

27 ms

nav-dropdown.svg

nav-dropdown.svg

37 ms

nav-dropdown-black.svg

nav-dropdown-black.svg

65 ms

cloud.svg

cloud.svg

87 ms

menu-cloud-private.svg

menu-cloud-private.svg

89 ms

menu-cloud-apps.svg

menu-cloud-apps.svg

86 ms

menu-sap.svg

menu-sap.svg

90 ms

IP-Transit.svg

IP-Transit.svg

92 ms

Dark-fiber.svg

Dark-fiber.svg

93 ms

Ethernet.svg

Ethernet.svg

118 ms

data-centers-h.svg

data-centers-h.svg

116 ms

Bare-metal-server.svg

Bare-metal-server.svg

114 ms

footer-logo.svg

footer-logo.svg

120 ms

twitter-x.svg

twitter-x.svg

118 ms

LinkedIn%20-%20Dark.svg

LinkedIn%20-%20Dark.svg

122 ms

Discord%20-%20Dark.svg

Discord%20-%20Dark.svg

145 ms

Envelope.svg

Envelope.svg

143 ms

database.svg

database.svg

146 ms

Back.svg

Back.svg

147 ms

clock.svg

clock.svg

149 ms

zap.svg

zap.svg

150 ms

Accessibility Review

kapany.net accessibility score

84

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.

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 IDs are not unique

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

Image elements do not have [alt] attributes

Best Practices

kapany.net 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

High

Page has valid source maps

SEO Factors

kapany.net 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 Kapany.net 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 Kapany.net 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

kapany.net

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