2.1 sec in total
39 ms
1.5 sec
543 ms
Welcome to kiniksa.com homepage info - get ready to check Kiniksa best content right away, or after learning these important things about kiniksa.com
Kiniksa Pharmaceuticals is a biopharmaceutical company that believes every second makes a difference for patients living with debilitating diseases.
Visit kiniksa.comWe analyzed Kiniksa.com page load time and found that the first response time was 39 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
kiniksa.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value13.7 s
0/100
25%
Value10.7 s
7/100
10%
Value19,370 ms
0/100
30%
Value0.178
68/100
15%
Value38.3 s
0/100
10%
39 ms
30 ms
25 ms
62 ms
17 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 30% of them (24 requests) were addressed to the original Kiniksa.com, 10% (8 requests) were made to Fonts.gstatic.com and 10% (8 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (662 ms) relates to the external source Player.vimeo.com.
Page size can be reduced by 312.1 kB (9%)
3.4 MB
3.1 MB
In fact, the total size of Kiniksa.com main page is 3.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. 75% 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 2.6 MB which makes up the majority of the site volume.
Potential reduce by 134.0 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 134.0 kB or 81% of the original size.
Potential reduce by 175.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. Kiniksa images are well optimized though.
Potential reduce by 2.7 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 228 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. Kiniksa.com has all CSS files already compressed.
Number of requests can be reduced by 24 (35%)
68
44
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kiniksa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
kiniksa.com
39 ms
kiniksa.com
30 ms
www.kiniksa.com
25 ms
plugin.js
62 ms
css_zZM_pXhmhroWGDZynGPQXiS5IGMKvP9K548lgZ19eUQ.css
17 ms
embed.css
43 ms
css_HMy2GalHosdDI6xVWoqid9gXvlCYSg-fVkrf1ITTdUg.css
23 ms
css_Kn_GoxubrW0Y55pohBxAEWwYSkpWFeAmqRpUyoB9ZCg.css
27 ms
js_T8YVOOttNfmFJd_HtCarZL6AinLnJZoHK07dz1ODcO0.js
25 ms
otSDKStub.js
43 ms
js_bxT4GFNfXnTnz9RWnSXmU8dQgEal6UxDYeF3jCxZzFM.js
23 ms
contact_us
84 ms
js_eBjObyCh_IrEoSw1bqCpW_3U57sfgZtFh3E0q0iN2j4.js
35 ms
embed-no-jquery.js
60 ms
js_6hkrnwjtibw-hQnIfxZYf16TY6qOsevwsjMaXnCRQ7M.js
35 ms
css2
39 ms
css2
56 ms
9881d70e-9e2e-481d-b8bd-bb0e9f023250.json
23 ms
form_81be99432b.js
121 ms
logo.png
29 ms
thumbnail-jp-morgan-conference.jpg
20 ms
careers_video_2_0_0.png
55 ms
kiniksa-logo.png
19 ms
location
30 ms
otBannerSdk.js
13 ms
en.json
17 ms
otFlat.json
39 ms
otPcCenter.json
90 ms
Vanessa_0.png
244 ms
oembed
62 ms
901465097
352 ms
oembed
115 ms
ccOGvnkTDOo
227 ms
499382304
345 ms
463123317
662 ms
499685955
662 ms
video_play.svg
109 ms
Jill.png
222 ms
Nadine.png
217 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
227 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
267 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
283 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
290 ms
css_sZBvEXHNWqkDz7pt6i-IYnytiV_uEKTrslOEPw1AtdA.css
169 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvUDQ.ttf
220 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTbtY.ttf
194 ms
gtm.js
572 ms
enrich
517 ms
KINIKSA-_reversed_tagline.png
112 ms
poweredBy_ot_logo.svg
58 ms
www-player.css
30 ms
www-embed-player.js
93 ms
base.js
126 ms
1034282443-40b677a53f627c9441f44f79a986d6764b6bf913b290b77f86397294f03b5b12-d
426 ms
kiniksa
398 ms
1780380927-1b24256565f98580fcc9c93853f17a57658b77eb9a23242c2dfe20bbc3f3f22c-d
394 ms
ad_status.js
375 ms
ZkUM7HQKzcKWL-DM3yo4WGnr3mDsumI-oijucI1qrYc.js
283 ms
embed.js
96 ms
968327582-e6938a41a649e0dee83fa28bbf2856372d429823ba36287045e164509916500a-d
158 ms
1034285151-bbf2e299db12ac04c5e114a78cc6f19d3e0f2b64975d7fdf539013549ab5954b-d
157 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
100 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
100 ms
twitter-reply-gray.png
109 ms
poster_images.jpg
68 ms
images.jpg
284 ms
poster_images.jpg
86 ms
images.jpg
285 ms
poster_images.jpg
79 ms
images.jpg
92 ms
twitter-retweet-gray.png
85 ms
twitter-like-gray.png
77 ms
gallery.png
78 ms
icon-twitter-reply.svg
62 ms
fontawesome-5-juicer.woff
277 ms
icon-twitter-retweet.svg
62 ms
icon-twitter-like.svg
61 ms
Create
244 ms
Create
322 ms
id
19 ms
kiniksa.com accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
kiniksa.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
kiniksa.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 Kiniksa.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 Kiniksa.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.
kiniksa.com
Open Graph description is not detected on the main page of Kiniksa. 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: