Tools & Wizards About Us
gleostine.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

gleostine.com

Gleostine® | For Patients with Brain Cancer or Hodgkin's Disease

Page Load Speed

2.9 sec in total

First Response

664 ms

Resources Loaded

2 sec

Page Rendered

238 ms

gleostine.com screenshot

About Website

Welcome to gleostine.com homepage info - get ready to check Gleostine best content right away, or after learning these important things about gleostine.com

Gleostine® (lomustine) is an alkylating drug indicated for the treatment of patients with primary and metastatic brain tumors and/or Hodgkin's lymphoma.

Visit gleostine.com

Key Findings

We analyzed Gleostine.com page load time and found that the first response time was 664 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

gleostine.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,100 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

gleostine.com

664 ms

wp-emoji-release.min.js

55 ms

style.min.css

107 ms

advanced-floating-content-public.css

158 ms

styles.css

161 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 81% of them (59 requests) were addressed to the original Gleostine.com, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (664 ms) belongs to the original domain Gleostine.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 81.2 kB (6%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gleostine.com main page is 1.4 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. 70% of websites need less resources to load. Images take 764.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 64.9 kB

  • Original 80.1 kB
  • After minification 77.0 kB
  • After compression 15.2 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 64.9 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 5.3 kB

  • Original 764.6 kB
  • After minification 759.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. Gleostine images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.2 kB

  • Original 408.3 kB
  • After minification 407.9 kB
  • After compression 405.1 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

-6%

Potential reduce by 7.7 kB

  • Original 134.2 kB
  • After minification 134.1 kB
  • After compression 126.5 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. Gleostine.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 55 (83%)

Requests Now

66

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gleostine.com

gleostine.com

664 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

55 ms

style.min.css

style.min.css

107 ms

advanced-floating-content-public.css

advanced-floating-content-public.css

158 ms

styles.css

styles.css

161 ms

jquery.mb.YTPlayer.min.css

jquery.mb.YTPlayer.min.css

159 ms

dex-mlp-front.css

dex-mlp-front.css

158 ms

widget-options.css

widget-options.css

159 ms

animate.min.css

animate.min.css

161 ms

settings.css

settings.css

212 ms

bootstrap.min.css

bootstrap.min.css

218 ms

jquery.fancybox.css

jquery.fancybox.css

214 ms

owl.carousel.css

owl.carousel.css

210 ms

odometer-theme-default.css

odometer-theme-default.css

214 ms

animate.min.css

animate.min.css

215 ms

font-awesome.min.css

font-awesome.min.css

265 ms

halcyon-icons.min.css

halcyon-icons.min.css

264 ms

style.css

style.css

272 ms

css

css

37 ms

js_composer.min.css

js_composer.min.css

280 ms

jquery.js

jquery.js

321 ms

jquery-migrate.min.js

jquery-migrate.min.js

265 ms

advanced-floating-content-public.js

advanced-floating-content-public.js

314 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

319 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

422 ms

jq-sticky-anything.min.js

jq-sticky-anything.min.js

343 ms

css

css

53 ms

js

js

65 ms

scripts.js

scripts.js

343 ms

jquery.stellar.min.js

jquery.stellar.min.js

366 ms

jquery.mb.YTPlayer.min.js

jquery.mb.YTPlayer.min.js

372 ms

dex-mlp-front.js

dex-mlp-front.js

370 ms

jquery.widgetopts.min.js

jquery.widgetopts.min.js

373 ms

portfolio_ajax.js

portfolio_ajax.js

376 ms

stickThis.js

stickThis.js

418 ms

bootstrap.min.js

bootstrap.min.js

436 ms

jquery.viewport.js

jquery.viewport.js

435 ms

hoverIntent.min.js

hoverIntent.min.js

436 ms

superfish.js

superfish.js

436 ms

js

js

54 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

477 ms

owl.carousel.min.js

owl.carousel.min.js

504 ms

imagesloaded.min.js

imagesloaded.min.js

415 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

364 ms

gmap3.min.js

gmap3.min.js

363 ms

jquery.easypiechart.min.js

jquery.easypiechart.min.js

362 ms

jquerysimplecounter.js

jquerysimplecounter.js

397 ms

odometer.min.js

odometer.min.js

404 ms

chart.min.js

chart.min.js

453 ms

instafeed.min.js

instafeed.min.js

355 ms

twitterfetcher.min.js

twitterfetcher.min.js

353 ms

wow.min.js

wow.min.js

376 ms

custom.js

custom.js

377 ms

wp-embed.min.js

wp-embed.min.js

368 ms

js_composer_front.min.js

js_composer_front.min.js

392 ms

gleaosrine_logo-01.png

gleaosrine_logo-01.png

212 ms

older_couple_B.jpg

older_couple_B.jpg

357 ms

nextsource_care_logo_full_color_low_rez-1-300x99.png

nextsource_care_logo_full_color_low_rez-1-300x99.png

87 ms

careGiver.jpg

careGiver.jpg

130 ms

logo_footer.png

logo_footer.png

305 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

40 ms

gloestine_website_image_blue_9.jpg

gloestine_website_image_blue_9.jpg

336 ms

gloestine_website_image_01-1.jpg

gloestine_website_image_01-1.jpg

209 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

34 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

35 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

260 ms

js

js

53 ms

analytics.js

analytics.js

30 ms

collect

collect

52 ms

js

js

48 ms

collect

collect

30 ms

Accessibility Review

gleostine.com accessibility score

64

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

gleostine.com 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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

gleostine.com SEO score

82

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

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

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

gleostine.com

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