Tools & Wizards About Us
tmpn.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

tmpn.com

Taurus Maintenance Products Namibia | Cleaning Producs & Equipment

Page Load Speed

3.9 sec in total

First Response

278 ms

Resources Loaded

3.3 sec

Page Rendered

290 ms

tmpn.com screenshot

About Website

Visit tmpn.com now to see the best up-to-date Tmpn content and also check out these interesting facts you probably never knew about tmpn.com

Taurus Maintenance Products is Namibia's leading manufacturer and supplier of cleaning chemicals and equipment.

Visit tmpn.com

Key Findings

We analyzed Tmpn.com page load time and found that the first response time was 278 ms and then it took 3.6 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

tmpn.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value3,040 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

tmpn.com

278 ms

www.tmpn.com

706 ms

website.css

411 ms

pr_sfx-base_1.css

451 ms

pa_sfx-home_1.css

521 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 68% of them (50 requests) were addressed to the original Tmpn.com, 15% (11 requests) were made to Static.xx.fbcdn.net and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Tmpn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 897.6 kB (54%)

Content Size

1.7 MB

After Optimization

780.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tmpn.com main page is 1.7 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. 65% of websites need less resources to load. Images take 679.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 207.9 kB

  • Original 238.6 kB
  • After minification 237.3 kB
  • After compression 30.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 207.9 kB or 87% of the original size.

Image Optimization

-17%

Potential reduce by 112.8 kB

  • Original 679.1 kB
  • After minification 566.3 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, Tmpn needs image optimization as it can save up to 112.8 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 381.8 kB

  • Original 530.3 kB
  • After minification 505.2 kB
  • After compression 148.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 381.8 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 195.0 kB

  • Original 229.6 kB
  • After minification 191.9 kB
  • After compression 34.5 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. Tmpn.com needs all CSS files to be minified and compressed as it can save up to 195.0 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

70

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tmpn.com

tmpn.com

278 ms

www.tmpn.com

www.tmpn.com

706 ms

website.css

website.css

411 ms

pr_sfx-base_1.css

pr_sfx-base_1.css

451 ms

pa_sfx-home_1.css

pa_sfx-home_1.css

521 ms

index1.css

index1.css

487 ms

index2.css

index2.css

541 ms

global.css

global.css

519 ms

global-responsive.css

global-responsive.css

621 ms

box.css

box.css

628 ms

content.css

content.css

902 ms

style.css

style.css

743 ms

flickity.min.css

flickity.min.css

742 ms

loader.js

loader.js

881 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

923 ms

jquery.sidr.min.js

jquery.sidr.min.js

802 ms

sf.js

sf.js

1346 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

1125 ms

jquery.zoom.min.js

jquery.zoom.min.js

998 ms

echo.js

echo.js

1016 ms

js

js

84 ms

sharethis.js

sharethis.js

41 ms

js

js

128 ms

widgets.js

widgets.js

262 ms

jquery.menu-aim.js

jquery.menu-aim.js

1066 ms

jquery.megamenu.js

jquery.megamenu.js

1066 ms

ellipsis-text.js

ellipsis-text.js

997 ms

date.js

date.js

232 ms

WidgetScript

WidgetScript

78 ms

fbevents.js

fbevents.js

78 ms

56rni0vdus

56rni0vdus

128 ms

extra.html

extra.html

264 ms

trans.gif

trans.gif

355 ms

k_sq-mitsuki-new.png

k_sq-mitsuki-new.png

571 ms

k_Floorfresh.png

k_Floorfresh.png

571 ms

k_alcolin-competition.png

k_alcolin-competition.png

571 ms

sf-darken.png

sf-darken.png

512 ms

icomoon.ttf

icomoon.ttf

523 ms

clarity.js

clarity.js

27 ms

dynamic.html

dynamic.html

583 ms

cload.html

cload.html

518 ms

lang.html

lang.html

517 ms

page.php

page.php

224 ms

load_dynamic_js.js

load_dynamic_js.js

437 ms

front_.js

front_.js

464 ms

v7ping.js

v7ping.js

160 ms

menu_scroller.js

menu_scroller.js

409 ms

d-34.html

d-34.html

384 ms

d-33.html

d-33.html

469 ms

next-sprite.png

next-sprite.png

508 ms

MKheCYCMdiz.css

MKheCYCMdiz.css

56 ms

39kC6vylKLb.js

39kC6vylKLb.js

120 ms

ghMUHoxvkNp.js

ghMUHoxvkNp.js

158 ms

r6Ea-0PXa8H.js

r6Ea-0PXa8H.js

165 ms

tC2E_WEPqHv.js

tC2E_WEPqHv.js

164 ms

58N-KqTOr1w.js

58N-KqTOr1w.js

164 ms

p55HfXW__mM.js

p55HfXW__mM.js

163 ms

KroQaZupEyF.js

KroQaZupEyF.js

163 ms

6a0tO5GYL5B.js

6a0tO5GYL5B.js

160 ms

taurus-maintenance-namibia.png

taurus-maintenance-namibia.png

393 ms

b_spring2024.png

b_spring2024.png

670 ms

458173284_924865202994313_3970497604216364170_n.jpg

458173284_924865202994313_3970497604216364170_n.jpg

55 ms

hFp8JbjxADj.js

hFp8JbjxADj.js

21 ms

289858743_410983751049130_5099845288150710090_n.png

289858743_410983751049130_5099845288150710090_n.png

56 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

18 ms

v6.js

v6.js

75 ms

lang_en-us.js

lang_en-us.js

202 ms

trans.gif

trans.gif

148 ms

load_productmediashare.html

load_productmediashare.html

237 ms

conf.html

conf.html

190 ms

grey.html

grey.html

187 ms

d98_404.html

d98_404.html

327 ms

cntyList.js

cntyList.js

215 ms

contactus_address.js

contactus_address.js

233 ms

Accessibility Review

tmpn.com accessibility score

55

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

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

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

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

High

Form elements do not have associated labels

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

tmpn.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tmpn.com SEO score

91

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tmpn.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 Tmpn.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

tmpn.com

Open Graph description is not detected on the main page of Tmpn. 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: