Tools & Wizards About Us
prosman.in screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

prosman.in

Chereso Health – Chereso Health

Page Load Speed

4.2 sec in total

First Response

465 ms

Resources Loaded

3.3 sec

Page Rendered

438 ms

prosman.in screenshot

About Website

Click here to check amazing Prosman content for Nigeria. Otherwise, check out these important facts you probably never knew about prosman.in

Visit prosman.in

Key Findings

We analyzed Prosman.in page load time and found that the first response time was 465 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

prosman.in performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value2,990 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.261

47/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

prosman.in

465 ms

cheresohealth.com

456 ms

style.min.css

178 ms

wc-blocks-vendors-style.css

177 ms

wc-blocks-style.css

243 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Prosman.in, 81% (101 requests) were made to Cheresohealth.com and 10% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cheresohealth.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 762.1 kB (30%)

Content Size

2.5 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prosman.in main page is 2.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. 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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 207.9 kB

  • Original 234.5 kB
  • After minification 188.5 kB
  • After compression 26.6 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 46.0 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 207.9 kB or 89% of the original size.

Image Optimization

-25%

Potential reduce by 311.9 kB

  • Original 1.2 MB
  • After minification 918.0 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. Obviously, Prosman needs image optimization as it can save up to 311.9 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 112.4 kB

  • Original 743.2 kB
  • After minification 742.8 kB
  • After compression 630.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 112.4 kB or 15% of the original size.

CSS Optimization

-41%

Potential reduce by 129.9 kB

  • Original 315.8 kB
  • After minification 315.8 kB
  • After compression 185.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. Prosman.in needs all CSS files to be minified and compressed as it can save up to 129.9 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (80%)

Requests Now

101

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prosman.in

prosman.in

465 ms

cheresohealth.com

cheresohealth.com

456 ms

style.min.css

style.min.css

178 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

177 ms

wc-blocks-style.css

wc-blocks-style.css

243 ms

frontend.css

frontend.css

251 ms

badges.css

badges.css

183 ms

owl.carousel.min.css

owl.carousel.min.css

38 ms

owl.theme.default.css

owl.theme.default.css

53 ms

woocommerce-layout.css

woocommerce-layout.css

190 ms

twenty-twenty.css

twenty-twenty.css

236 ms

xoo-wsc-fonts.css

xoo-wsc-fonts.css

240 ms

xoo-wsc-style.css

xoo-wsc-style.css

255 ms

style.css

style.css

316 ms

elementor-icons.min.css

elementor-icons.min.css

300 ms

animations.min.css

animations.min.css

297 ms

frontend-legacy.min.css

frontend-legacy.min.css

299 ms

frontend.min.css

frontend.min.css

309 ms

post-11.css

post-11.css

302 ms

frontend.min.css

frontend.min.css

368 ms

global.css

global.css

1133 ms

post-146.css

post-146.css

359 ms

post-136.css

post-136.css

365 ms

post-204.css

post-204.css

377 ms

elementor-fix.css

elementor-fix.css

378 ms

photoswipe.min.css

photoswipe.min.css

419 ms

default-skin.min.css

default-skin.min.css

426 ms

style.css

style.css

427 ms

frontend.css

frontend.css

429 ms

css

css

41 ms

fontawesome.min.css

fontawesome.min.css

435 ms

solid.min.css

solid.min.css

478 ms

brands.min.css

brands.min.css

485 ms

regular.min.css

regular.min.css

487 ms

jquery.min.js

jquery.min.js

495 ms

jquery-migrate.min.js

jquery-migrate.min.js

495 ms

analytics-talk-content-tracking.js

analytics-talk-content-tracking.js

537 ms

gtm4wp-woocommerce-classic.js

gtm4wp-woocommerce-classic.js

545 ms

gtm4wp-woocommerce-enhanced.js

gtm4wp-woocommerce-enhanced.js

551 ms

index.js

index.js

559 ms

js

js

73 ms

owl.carousel.min.js

owl.carousel.min.js

10 ms

api.js

api.js

35 ms

animate.css

animate.css

461 ms

line-awesome.css

line-awesome.css

432 ms

simple-line-icons.css

simple-line-icons.css

437 ms

theme.css

theme.css

440 ms

featherlight.css

featherlight.css

438 ms

style.css

style.css

395 ms

owl.carousel.css

owl.carousel.css

418 ms

post-41418.css

post-41418.css

427 ms

post-766.css

post-766.css

426 ms

hooks.min.js

hooks.min.js

433 ms

wpm-public.p1.min.js

wpm-public.p1.min.js

401 ms

frontend.js

frontend.js

427 ms

colcade.js

colcade.js

435 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

439 ms

add-to-cart.min.js

add-to-cart.min.js

434 ms

js.cookie.min.js

js.cookie.min.js

439 ms

woocommerce.min.js

woocommerce.min.js

428 ms

cart-fragments.min.js

cart-fragments.min.js

430 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

640 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

428 ms

photoswipe.min.js

photoswipe.min.js

443 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

428 ms

index.js

index.js

431 ms

xoo-wsc-main.js

xoo-wsc-main.js

440 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

455 ms

imagesloaded.min.js

imagesloaded.min.js

470 ms

featherlight.js

featherlight.js

441 ms

custom.js

custom.js

444 ms

owl.carousel.min.js

owl.carousel.min.js

460 ms

frontend-modules.min.js

frontend-modules.min.js

477 ms

jquery.sticky.min.js

jquery.sticky.min.js

486 ms

frontend.min.js

frontend.min.js

513 ms

core.min.js

core.min.js

465 ms

dialog.min.js

dialog.min.js

482 ms

waypoints.min.js

waypoints.min.js

484 ms

swiper.min.js

swiper.min.js

517 ms

share-link.min.js

share-link.min.js

475 ms

frontend.min.js

frontend.min.js

621 ms

fbevents.js

fbevents.js

129 ms

gtm.js

gtm.js

734 ms

CHERESO-LOGO1.svg

CHERESO-LOGO1.svg

215 ms

logo-final00.png

logo-final00.png

217 ms

WhatsApp-Image-2023-03-18-at-10.53.28-AM.jpeg

WhatsApp-Image-2023-03-18-at-10.53.28-AM.jpeg

509 ms

mobile-banner-3.jpg

mobile-banner-3.jpg

509 ms

WhatsApp-Image-2023-03-18-at-10.53.29-AM.jpeg

WhatsApp-Image-2023-03-18-at-10.53.29-AM.jpeg

508 ms

21r6i9pVwLL-1-300x300.jpg

21r6i9pVwLL-1-300x300.jpg

387 ms

img-1-1-300x300.jpg

img-1-1-300x300.jpg

507 ms

pro-4-300x300.jpg

pro-4-300x300.jpg

508 ms

gcb-removebg-preview-300x300.png

gcb-removebg-preview-300x300.png

687 ms

prosman-300x300.jpg

prosman-300x300.jpg

687 ms

Furosap-30-300x300.jpg

Furosap-30-300x300.jpg

687 ms

bgg11.jpg

bgg11.jpg

812 ms

chereso-1.jpg

chereso-1.jpg

687 ms

logo_2.png

logo_2.png

811 ms

logo.png

logo.png

812 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

110 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

113 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

284 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

285 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

284 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

283 ms

fa-solid-900.woff

fa-solid-900.woff

608 ms

fa-regular-400.woff

fa-regular-400.woff

608 ms

fa-brands-400.woff

fa-brands-400.woff

784 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

278 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf

278 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

278 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

278 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

278 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

279 ms

init.js

init.js

461 ms

up-2.jpg

up-2.jpg

559 ms

about-bg-1-1.jpg

about-bg-1-1.jpg

558 ms

Woo-Side-Cart.woff

Woo-Side-Cart.woff

480 ms

recaptcha__en.js

recaptcha__en.js

268 ms

cheresohealth.com

cheresohealth.com

508 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

193 ms

star.woff

star.woff

194 ms

bundle.js

bundle.js

100 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

64 ms

print.css

print.css

62 ms

Accessibility Review

prosman.in accessibility score

87

Accessibility Issues

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-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

Links do not have a discernible name

Best Practices

prosman.in best practices score

75

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

prosman.in SEO score

86

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 Prosman.in 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 Prosman.in 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

prosman.in

Open Graph description is not detected on the main page of Prosman. 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: