Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

tikamobile.com

TikaMobile: CRM for Life Sciences, Medical Device, Pharma Sales Reps

Page Load Speed

11.4 sec in total

First Response

273 ms

Resources Loaded

4.2 sec

Page Rendered

6.9 sec

tikamobile.com screenshot

About Website

Click here to check amazing Tika Mobile content for United States. Otherwise, check out these important facts you probably never knew about tikamobile.com

Make your sales reps smarter by using our mobile CRM & Business Intelligence solution. Empower reps with the latest information on their customers. Specifically designed for life sciences, pharmaceuti...

Visit tikamobile.com

Key Findings

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

Performance Metrics

tikamobile.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value24.2 s

0/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.106

88/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

www.tikamobile.com

273 ms

Custom_main.min.css

375 ms

bootstrap.min.css

471 ms

module_37805554614_Main_Header.min.css

379 ms

module_38258332785_Home_Page_Slider.min.css

377 ms

Our browser made a total of 175 requests to load all elements on the main page. We found that 31% of them (54 requests) were addressed to the original Tikamobile.com, 46% (80 requests) were made to Fonts.gstatic.com and 5% (8 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Tikamobile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (17%)

Content Size

11.8 MB

After Optimization

9.9 MB

In fact, the total size of Tikamobile.com main page is 11.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. 85% 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 11.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 49.3 kB

  • Original 62.0 kB
  • After minification 56.6 kB
  • After compression 12.6 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 49.3 kB or 80% of the original size.

Image Optimization

-16%

Potential reduce by 1.9 MB

  • Original 11.7 MB
  • After minification 9.8 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, Tika Mobile needs image optimization as it can save up to 1.9 MB or 16% 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 173 B

  • Original 41.5 kB
  • After minification 41.5 kB
  • After compression 41.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

-17%

Potential reduce by 3.4 kB

  • Original 20.4 kB
  • After minification 20.4 kB
  • After compression 17.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. Tikamobile.com needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (48%)

Requests Now

92

After Optimization

48

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

Accessibility Review

tikamobile.com accessibility score

79

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

[role] values are not valid

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

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tikamobile.com SEO score

71

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tikamobile.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 Tikamobile.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 Tika Mobile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: