3.5 sec in total
108 ms
3 sec
338 ms
Visit onfi.com now to see the best up-to-date ONFI content and also check out these interesting facts you probably never knew about onfi.com
ONFI® (clobazam) can treat seizures related to Lennox-Gastaut syndrome in people 2 years of age or older. See full prescribing information and boxed WARNING.
Visit onfi.comWe analyzed Onfi.com page load time and found that the first response time was 108 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
onfi.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value5.7 s
17/100
25%
Value4.7 s
69/100
10%
Value1,250 ms
19/100
30%
Value0.23
54/100
15%
Value11.0 s
20/100
10%
108 ms
33 ms
85 ms
109 ms
72 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 57% of them (27 requests) were addressed to the original Onfi.com, 6% (3 requests) were made to S7.addthis.com and 6% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (733 ms) belongs to the original domain Onfi.com.
Page size can be reduced by 132.2 kB (11%)
1.2 MB
1.0 MB
In fact, the total size of Onfi.com main page is 1.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. 65% of websites need less resources to load. Images take 769.9 kB which makes up the majority of the site volume.
Potential reduce by 99.5 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 99.5 kB or 77% of the original size.
Potential reduce by 23.3 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. ONFI images are well optimized though.
Potential reduce by 9.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. This website has mostly compressed JavaScripts.
Potential reduce by 30 B
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. Onfi.com has all CSS files already compressed.
Number of requests can be reduced by 26 (68%)
38
12
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ONFI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.onfi.com
108 ms
clientlibs-reset.min.b4d340bc707eda953022ec36b3666e1a.css
33 ms
clientlibs-bootstrap.min.699a311fb37b11ff4120fd901a2971c4.css
85 ms
clientlibs-onfi.min.f711bc02a6e810a43c767b459eaf97c8.css
109 ms
main.min.e1f12da26d615c8dbcd02dc04eca9aa3.css
72 ms
jquery.min.js
77 ms
utils.min.js
72 ms
granite.min.js
75 ms
jquery.min.js
98 ms
shared.min.js
178 ms
main.min.js
180 ms
launch-EN0972a5c5801e413ca72f96a190e0e241.min.js
512 ms
addthis_widget.js
198 ms
api.js
357 ms
contexthub.kernel.js
187 ms
clientlibs-jquery.min.js
196 ms
clientlibs-bootstrap.min.js
355 ms
clientlibs-onfi.min.js
355 ms
token.json
337 ms
moatframe.js
487 ms
logo-onfi.png
691 ms
dont-giveup-common.png
634 ms
lundbecklogo.png
636 ms
nav-main-bg.png
412 ms
subnav-bg.png
411 ms
home-hero.jpg
733 ms
recaptcha__en.js
454 ms
EXec1649d5dbd04c008b6afe49a8474ace-libraryCode_source.min.js
296 ms
4b978f72-bb48-46c3-909a-2a8cd2f8819c.woff
339 ms
75b36c58-2a02-4057-a537-09af0832ae46.woff
299 ms
61bd362e-7162-46bd-b67e-28f366c4afbe.woff
341 ms
icomoon.ttf
340 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
340 ms
6dc0e7d8-9284-44e1-8f05-984a41daa3a4.woff
374 ms
js
389 ms
_ate.track.config_resp
422 ms
300lo.json
405 ms
scroll-to-top-icon.png
161 ms
sh.f48a1a04fe8dbf021b4cda1d.html
109 ms
9bdf0737-f98c-477a-9365-ffc41b9d1285.ttf
102 ms
conversion_async.js
26 ms
96132a00-0376-4eb5-a388-520a30852b1b.js
257 ms
layers.fa6cd1947ce26e890d3d.js
29 ms
272 ms
26 ms
rd
7 ms
id
49 ms
onfi.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
onfi.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
onfi.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onfi.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 Onfi.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.
onfi.com
Open Graph data is detected on the main page of ONFI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: