1.9 sec in total
99 ms
1.2 sec
620 ms
Visit myfiasp.com now to see the best up-to-date My Fiasp content and also check out these interesting facts you probably never knew about myfiasp.com
Fiasp®, a rapid-acting insulin, is designed for people living with diabetes to help control blood sugar at mealtimes. Read important safety & prescribing info on this page.
Visit myfiasp.comWe analyzed Myfiasp.com page load time and found that the first response time was 99 ms and then it took 1.8 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.
myfiasp.com performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value11.2 s
0/100
25%
Value4.0 s
81/100
10%
Value3,090 ms
2/100
30%
Value1.289
1/100
15%
Value13.2 s
12/100
10%
99 ms
183 ms
66 ms
108 ms
177 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Myfiasp.com, 77% (60 requests) were made to Mynovoinsulin.com and 10% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (419 ms) relates to the external source Mynovoinsulin.com.
Page size can be reduced by 1.5 MB (81%)
1.8 MB
352.8 kB
In fact, the total size of Myfiasp.com main page is 1.8 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 121.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 121.5 kB or 89% of the original size.
Potential reduce by 1.3 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. Obviously, My Fiasp needs image optimization as it can save up to 1.3 MB or 96% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 988 B
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 10.2 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. Myfiasp.com needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 18% of the original size.
Number of requests can be reduced by 50 (75%)
67
17
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Fiasp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
myfiasp.com
99 ms
home.html
183 ms
clientlib-base.min.css
66 ms
clientlib-vendor.min.css
108 ms
jquery.min.js
177 ms
utils.min.js
106 ms
granite.min.js
112 ms
jquery.min.js
105 ms
clientlib-vendor.min.js
243 ms
clientlib-custom-grid.min.css
136 ms
site.min.css
154 ms
clientlibs.min.css
156 ms
clientlibs-web.min.css
157 ms
clientlibs.min.css
168 ms
globalnavigation.min.css
170 ms
clientlibs.min.js
172 ms
clientlibs.min.css
172 ms
clientlibs.min.js
243 ms
clientlibs.min.css
244 ms
clientlibs.min.js
244 ms
clientlibs-bubble.min.js
246 ms
clientlibs.min.css
247 ms
clientlib-analytics.min.js
248 ms
clientlibs.min.js
249 ms
clientlibs.min.css
249 ms
clientlibs.min.js
250 ms
clientlibs-all.min.css
228 ms
clientlibs-web.min.css
229 ms
clientlibs-web.min.css
240 ms
fisasp-consumer.css
269 ms
clientlibs-web.min.js
242 ms
clientlibs-web.min.js
269 ms
clientlibs.min.css
270 ms
site.min.css
271 ms
mynovoinsulin_js_global.js
323 ms
mynovoinsulin_js_fiasp.js
324 ms
mynovoinsulin_style_fiasp.css
324 ms
site.min.js
253 ms
container.min.js
253 ms
clientlib-base.min.js
249 ms
gtm.js
161 ms
fiasp-logo.png
207 ms
mni-icon-megamenu-supportprogramoverview.svg
207 ms
mni-icon-megamenu-aboutdiabetes.svg
208 ms
mni-icon-megamenu-managingdiabetes.svg
207 ms
mni-icon-megamenu-allabouttype1.svg
209 ms
transparent-arrow.png
222 ms
fsp-icon-startworkingfast.png
223 ms
fsp-icon-penvial.png
221 ms
fsp-icon-copaysavcard.png
221 ms
token.json
154 ms
novo-nordisk-logo.svg
148 ms
home.html
186 ms
mynovoinsulin_style_global.css
70 ms
css2
57 ms
otSDKStub.js
46 ms
datalayer.js
33 ms
glueframe-1.1.3.js
9 ms
tbp6tqr.css
43 ms
mynovoinsulin_style_global_header.css
34 ms
mynovoinsulin_style_isi.css
37 ms
mynovoinsulin_style_global_footer.css
38 ms
font-awesome.min.css
35 ms
f2a0a6c7-69b1-45ee-ac57-1067f82c5cba.json
30 ms
otBannerSdk.js
21 ms
p.css
39 ms
sophia-72x82.png
67 ms
FSP-home-hero.png
419 ms
arrow-up.svg
56 ms
d
33 ms
d
72 ms
d
73 ms
d
73 ms
d
34 ms
d
15 ms
d
71 ms
icomoon.ttf
44 ms
FrutigerLTStd-Bold.woff
43 ms
myfiasp.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
myfiasp.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
myfiasp.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myfiasp.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 Myfiasp.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.
myfiasp.com
Open Graph data is detected on the main page of My Fiasp. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: