2.4 sec in total
291 ms
1.3 sec
800 ms
Welcome to viff.dk homepage info - get ready to check Viff best content right away, or after learning these important things about viff.dk
Archive of the VIFF project, active from 2007 to 2010. Please see https://github.com/github.com/data61/MP-SPDZ for an alternative. - GitHub - mgeisler/viff: Archive of the VIFF project, active from...
Visit viff.dkWe analyzed Viff.dk page load time and found that the first response time was 291 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.
viff.dk performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.5 s
65/100
25%
Value3.9 s
82/100
10%
Value330 ms
75/100
30%
Value0
100/100
15%
Value6.1 s
64/100
10%
291 ms
548 ms
162 ms
159 ms
278 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Viff.dk, 87% (45 requests) were made to Github.githubassets.com and 10% (5 requests) were made to Avatars.githubusercontent.com. The less responsive or slowest element that took the longest time to load (548 ms) relates to the external source Github.com.
Page size can be reduced by 163.0 kB (51%)
321.8 kB
158.8 kB
In fact, the total size of Viff.dk main page is 321.8 kB. 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. HTML takes 187.9 kB which makes up the majority of the site volume.
Potential reduce by 156.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 156.1 kB or 83% of the original size.
Potential reduce by 1.9 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. Obviously, Viff needs image optimization as it can save up to 1.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 5.0 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. Viff.dk has all CSS files already compressed.
Number of requests can be reduced by 43 (86%)
50
7
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
viff.dk
291 ms
viff
548 ms
light-5178aee0ee76.css
162 ms
dark-217d4f9c8e70.css
159 ms
primer-a8d2a8e3b2d5.css
278 ms
global-8b708e970131.css
236 ms
github-75abd9f1c887.css
198 ms
code-3d7b701fc6eb.css
167 ms
wp-runtime-c825a690093f.js
181 ms
vendors-node_modules_manuelpuyol_turbo_dist_turbo_es2017-esm_js-7ca92c8d513d.js
195 ms
vendors-node_modules_stacktrace-parser_dist_stack-trace-parser_esm_js-node_modules_github_bro-d351f6-c1d63d230b29.js
171 ms
environment-b63f7d2aa4d4.js
182 ms
vendors-node_modules_selector-observer_dist_index_esm_js-aefe1cd1c587.js
180 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_details-dialog-elemen-63debe-411ad558985a.js
189 ms
vendors-node_modules_github_auto-complete-element_dist_index_js-node_modules_github_catalyst_-6afc16-accdbcccdc1b.js
231 ms
vendors-node_modules_fzy_js_index_js-node_modules_github_markdown-toolbar-element_dist_index_js-6f74e8e38aad.js
191 ms
vendors-node_modules_github_time-elements_dist_index_js-74b4ec51ce20.js
271 ms
vendors-node_modules_github_file-attachment-element_dist_index_js-node_modules_github_filter--6a5bff-b71ed999fc05.js
362 ms
github-elements-e5f2533960fc.js
271 ms
element-registry-e00cc187980c.js
271 ms
vendors-node_modules_lit-html_lit-html_js-e954e8c01c93.js
270 ms
vendors-node_modules_github_mini-throttle_dist_index_js-node_modules_primer_behaviors_dist_es-899b47-60b74f01ac2c.js
526 ms
vendors-node_modules_github_paste-markdown_dist_index_esm_js-node_modules_koddsson_textarea-c-586f78-aad0fa01c792.js
525 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_scroll-anchoring_dist_scro-5881a7-8cc14636eb0d.js
511 ms
vendors-node_modules_github_alive-client_dist_index_js-node_modules_github_memoize_dist_esm_i-fab77c-ff9d9fde6bc6.js
511 ms
vendors-node_modules_github_filter-input-element_dist_index_js-node_modules_github_quote-sele-7bbf9f-45d498057c64.js
511 ms
app_assets_modules_github_updatable-content_ts-0a26daf35eaa.js
512 ms
app_assets_modules_github_sticky-scroll-into-view_ts-65a620396e37.js
512 ms
app_assets_modules_github_behaviors_keyboard-shortcuts-helper_ts-app_assets_modules_github_be-ac2ea2-30217e310469.js
515 ms
app_assets_modules_github_behaviors_commenting_edit_ts-app_assets_modules_github_behaviors_ht-83c235-106e3ba1cd01.js
513 ms
app_assets_modules_github_behaviors_batch-deferred-content_ts-app_assets_modules_github_behav-dc1370-97a0ccbc3aa2.js
513 ms
behaviors-273d350c1e03.js
523 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_catalyst_lib_index_js-06ff533-ac681f750823.js
513 ms
notifications-global-e71e7f99b10d.js
513 ms
vendors-node_modules_optimizely_optimizely-sdk_dist_optimizely_browser_es_min_js-node_modules-4de5ed-5896dc00fff4.js
519 ms
optimizely-290ece774b76.js
515 ms
vendors-node_modules_virtualized-list_es_index_js-node_modules_github_template-parts_lib_index_js-17ccfc4926a4.js
513 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-911b971-6879c2089889.js
516 ms
3272607
119 ms
20222909
290 ms
89623
452 ms
2234124
423 ms
73524876
423 ms
app_assets_modules_github_ref-selector_ts-8c0f66968207.js
378 ms
codespaces-827da8fcdd12.js
382 ms
vendors-node_modules_github_mini-throttle_dist_decorators_js-node_modules_github_remote-form_-0102c7-8caa4cfcee48.js
376 ms
vendors-node_modules_github_file-attachment-element_dist_index_js-node_modules_github_filter--705b26-2eefaf7c0bc2.js
361 ms
repositories-f20bf0827621.js
360 ms
topic-suggestions-581480b5d467.js
390 ms
code-menu-38863eeb396c.js
382 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-94fd67-0a275c70bcd7.js
381 ms
sessions-57098da4983d.js
380 ms
viff.dk 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
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
viff.dk 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
Page has valid source maps
viff.dk SEO score
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 Viff.dk 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 Viff.dk 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.
viff.dk
Open Graph data is detected on the main page of Viff. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: