Tools & Wizards About Us
nebido.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

nebido.com

Nebido® Testosterone Undecanoate Injection | Men's Health

Page Load Speed

7.7 sec in total

First Response

233 ms

Resources Loaded

7.3 sec

Page Rendered

138 ms

nebido.com screenshot

About Website

Click here to check amazing Nebido content for Palestinian Territory. Otherwise, check out these important facts you probably never knew about nebido.com

Visit nebido.com

Key Findings

We analyzed Nebido.com page load time and found that the first response time was 233 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

nebido.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

nebido.com

233 ms

nebido.com

362 ms

www.nebido.com

1346 ms

d667bcef392b.js

624 ms

jquery3.5.1.min.js

22 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 97% of them (124 requests) were addressed to the original Nebido.com, 1% (1 request) were made to Cdn.consentmanager.net and 1% (1 request) were made to Cdn.matomo.cloud. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Nebido.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 301.5 kB (27%)

Content Size

1.1 MB

After Optimization

820.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nebido.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. 55% of websites need less resources to load. Javascripts take 720.8 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 33.4 kB

  • Original 45.4 kB
  • After minification 42.3 kB
  • After compression 12.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.4 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 4.4 kB

  • Original 178.5 kB
  • After minification 174.1 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. Nebido images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 201.5 kB

  • Original 720.8 kB
  • After minification 718.3 kB
  • After compression 519.3 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 201.5 kB or 28% of the original size.

CSS Optimization

-35%

Potential reduce by 62.3 kB

  • Original 177.0 kB
  • After minification 177.0 kB
  • After compression 114.7 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. Nebido.com needs all CSS files to be minified and compressed as it can save up to 62.3 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 98 (88%)

Requests Now

112

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nebido.com

nebido.com

233 ms

nebido.com

nebido.com

362 ms

www.nebido.com

www.nebido.com

1346 ms

d667bcef392b.js

d667bcef392b.js

624 ms

jquery3.5.1.min.js

jquery3.5.1.min.js

22 ms

CookieHandler.js

CookieHandler.js

78 ms

mediaelementplayer.css

mediaelementplayer.css

239 ms

mediaelementplayer-legacy.css

mediaelementplayer-legacy.css

43 ms

font-awesomemin.css

font-awesomemin.css

44 ms

fullcalendar.css

fullcalendar.css

509 ms

jquerymcustomscrollbar.css

jquerymcustomscrollbar.css

585 ms

jquery-ui.css

jquery-ui.css

549 ms

author.css

author.css

55 ms

core.css

core.css

72 ms

file-type-icons.css

file-type-icons.css

84 ms

grayscale-mode.css

grayscale-mode.css

91 ms

reset.css

reset.css

455 ms

font-montserrat.css

font-montserrat.css

103 ms

nebido-style.css

nebido-style.css

129 ms

product-hub.css

product-hub.css

140 ms

font-glober.css

font-glober.css

258 ms

ie-origin-fix.js

ie-origin-fix.js

251 ms

xaquery.js

xaquery.js

1013 ms

moment.js

moment.js

1021 ms

lo-dash.js

lo-dash.js

489 ms

modernizr.js

modernizr.js

522 ms

galleria-157.js

galleria-157.js

1123 ms

fullcalendar.js

fullcalendar.js

1357 ms

gcal.js

gcal.js

566 ms

jqueryuitouch-punchmin.js

jqueryuitouch-punchmin.js

951 ms

hammer.js

hammer.js

596 ms

backbone-min.js

backbone-min.js

612 ms

typeahead.js

typeahead.js

655 ms

jquerymcustomscrollbar.js

jquerymcustomscrollbar.js

673 ms

flash-polyfill.js

flash-polyfill.js

688 ms

mediaelement-and-player.js

mediaelement-and-player.js

719 ms

dailymotion.js

dailymotion.js

734 ms

facebook.js

facebook.js

747 ms

soundcloud.js

soundcloud.js

1198 ms

twitch.js

twitch.js

978 ms

vimeo.js

vimeo.js

1351 ms

xa.js

xa.js

1369 ms

observer.js

observer.js

1361 ms

partial-design-highlight.js

partial-design-highlight.js

1090 ms

component-location-service.js

component-location-service.js

1467 ms

component-map.js

component-map.js

1143 ms

component-location-service.js

component-location-service.js

1548 ms

component-search.js

component-search.js

1675 ms

component-search-ajax.js

component-search-ajax.js

1631 ms

component-search-base-model.js

component-search-base-model.js

1650 ms

component-search-base-view.js

component-search-base-view.js

1627 ms

component-search-box.js

component-search-box.js

1505 ms

component-search-facet-data.js

component-search-facet-data.js

1403 ms

component-search-facet-summary.js

component-search-facet-summary.js

1401 ms

component-search-facet-dropdown.js

component-search-facet-dropdown.js

1217 ms

component-search-facet-managed-range.js

component-search-facet-managed-range.js

1199 ms

component-search-facet-range-slider.js

component-search-facet-range-slider.js

1536 ms

component-search-facet-slider.js

component-search-facet-slider.js

1250 ms

component-search-load-more.js

component-search-load-more.js

1555 ms

component-search-location-filter.js

component-search-location-filter.js

1212 ms

component-search-page-selector.js

component-search-page-selector.js

1625 ms

component-search-page-size.js

component-search-page-size.js

1535 ms

component-search-parameters.js

component-search-parameters.js

1272 ms

container_kFDnDP93.js

container_kFDnDP93.js

1019 ms

766382716

766382716

229 ms

Gx-toolkit.css

Gx-toolkit.css

1954 ms

component-search-query.js

component-search-query.js

1223 ms

component-search-radius-filter.js

component-search-radius-filter.js

1225 ms

component-search-results.js

component-search-results.js

1211 ms

component-search-results-count.js

component-search-results-count.js

1593 ms

component-search-results-filter.js

component-search-results-filter.js

1738 ms

api.js

api.js

10 ms

component-search-sort.js

component-search-sort.js

1532 ms

component-search-url.js

component-search-url.js

1601 ms

component-search-variant-filter.js

component-search-variant-filter.js

1564 ms

component-search-service.js

component-search-service.js

1325 ms

component-search-router.js

component-search-router.js

1607 ms

component-search-facet-daterange.js

component-search-facet-daterange.js

1356 ms

accessibility.js

accessibility.js

1709 ms

component-accordions.js

component-accordions.js

1302 ms

component-archive.js

component-archive.js

1174 ms

component-breadcrumb.js

component-breadcrumb.js

1177 ms

component-carousel.js

component-carousel.js

1176 ms

component-container.js

component-container.js

1535 ms

component-disqus.js

component-disqus.js

1416 ms

component-facebook.js

component-facebook.js

1363 ms

component-flash.js

component-flash.js

1345 ms

component-flip.js

component-flip.js

1180 ms

component-fullcalendar.js

component-fullcalendar.js

1530 ms

component-galleria.js

component-galleria.js

1549 ms

component-language-selector.js

component-language-selector.js

1578 ms

component-navigation.js

component-navigation.js

1566 ms

component-overlay.js

component-overlay.js

1241 ms

component-snippet.js

component-snippet.js

1247 ms

component-social.js

component-social.js

1614 ms

component-tabs.js

component-tabs.js

1605 ms

component-toggle.js

component-toggle.js

1429 ms

component-video.js

component-video.js

1717 ms

component-video-playlist.js

component-video-playlist.js

1355 ms

details-polyfill.js

details-polyfill.js

1351 ms

fixheight.js

fixheight.js

1705 ms

search-fixheight.js

search-fixheight.js

1276 ms

product-hub.js

product-hub.js

1221 ms

search.js

search.js

1599 ms

logo-grunenthal.svg

logo-grunenthal.svg

1129 ms

nebido_logo_250.png

nebido_logo_250.png

1019 ms

row_2_conversion_icon.png

row_2_conversion_icon.png

1010 ms

icon-colour-calculator.png

icon-colour-calculator.png

879 ms

icon-colour-management.png

icon-colour-management.png

883 ms

logo-nebido.png

logo-nebido.png

880 ms

logo-grunenthal.svg

logo-grunenthal.svg

871 ms

nebido_logo_250.png

nebido_logo_250.png

863 ms

hcp-modal-img1

hcp-modal-img1

867 ms

nebido_logo_250.png

nebido_logo_250.png

832 ms

prescribing_information_res_desk.jpg

prescribing_information_res_desk.jpg

1535 ms

www.nebido.com

www.nebido.com

2179 ms

visuelt-regular.woff

visuelt-regular.woff

1002 ms

visuelt-medium.woff

visuelt-medium.woff

932 ms

visuelt-bold.woff

visuelt-bold.woff

1221 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

1479 ms

OpenSans-Light_1.woff

OpenSans-Light_1.woff

1449 ms

OpenSans.woff

OpenSans.woff

1471 ms

icomoon.ttf

icomoon.ttf

1681 ms

icomoon_0.woff

icomoon_0.woff

1782 ms

OpenSans-Light_1.ttf

OpenSans-Light_1.ttf

627 ms

OpenSans-Bold.ttf

OpenSans-Bold.ttf

601 ms

OpenSans.ttf

OpenSans.ttf

569 ms

icomoon_0.ttf

icomoon_0.ttf

552 ms

Accessibility Review

nebido.com accessibility score

90

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

Image elements do not have [alt] attributes

Best Practices

nebido.com best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

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

nebido.com SEO score

68

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

High

Page is blocked from indexing

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Nebido.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 Nebido.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

nebido.com

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