Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fika.com

Gott kaffe på jobbet - Hyr kaffemaskin av Coffee Center

Page Load Speed

3.9 sec in total

First Response

349 ms

Resources Loaded

3.1 sec

Page Rendered

426 ms

About Website

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

Hyr en kaffemaskin av Coffee Center och luta dig tillbaka för fokusera på arbetet. Vårt fokus är att göra er fikapaus så njutbar som möjligt.

Visit fika.com

Key Findings

We analyzed Fika.com page load time and found that the first response time was 349 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

fika.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.103

89/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

fika.com

349 ms

coffeecenter.se

732 ms

javascript;base64,V2ViRm9udENvbmZpZz17Z29vZ2xlOntmYW1pbGllczpbIk1vbnRzZXJyYXQ6NDAwLDcwMCIsIk1hdGVyaWFsIEljb25zJmRpc3BsYXk9c3dhcCJdfX07aWYodHlwZW9mIFdlYkZvbnQ9PT0ib2JqZWN0IiYmdHlwZW9mIFdlYkZvbnQubG9hZD09PSJmdW5jdGlvbiIpe1dlYkZvbnQubG9hZChXZWJGb250Q29uZmlnKX0=

0 ms

webfontloader.min.js

208 ms

2119fdf7f26be46ca6734c15fcbeff49.css

185 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fika.com, 71% (56 requests) were made to Coffeecenter.se and 14% (11 requests) were made to . The less responsive or slowest element that took the longest time to load (932 ms) relates to the external source Coffeecenter.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 141.5 kB (21%)

Content Size

686.7 kB

After Optimization

545.2 kB

In fact, the total size of Fika.com main page is 686.7 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. Javascripts take 370.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 132.1 kB

  • Original 163.8 kB
  • After minification 163.1 kB
  • After compression 31.7 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 132.1 kB or 81% of the original size.

Image Optimization

-22%

Potential reduce by 7.3 kB

  • Original 33.5 kB
  • After minification 26.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. Obviously, Fika needs image optimization as it can save up to 7.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 979 B

  • Original 370.3 kB
  • After minification 370.3 kB
  • After compression 369.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.

CSS Optimization

-1%

Potential reduce by 1.1 kB

  • Original 119.0 kB
  • After minification 119.0 kB
  • After compression 117.9 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. Fika.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (66%)

Requests Now

59

After Optimization

20

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

Accessibility Review

fika.com accessibility score

72

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

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

<frame> or <iframe> elements do not have a title

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

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

Browser errors were logged to the console

SEO Factors

fika.com SEO score

90

Search Engine Optimization Advices

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

    SV

  • Language Claimed

    SV

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fika.com can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it matches the claimed language. Our system also found out that Fika.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

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