Tools & Wizards About Us
weetech.co.uk screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 0

    Best Practices

  • 75

    SEO

    Google-friendlier than
    32% of websites

weetech.co.uk

EPOS System for Takeaways - Online Ordering System| Weetech

Page Load Speed

1.9 sec in total

First Response

287 ms

Resources Loaded

1.5 sec

Page Rendered

73 ms

weetech.co.uk screenshot

About Website

Visit weetech.co.uk now to see the best up-to-date Weetech content for Iran and also check out these interesting facts you probably never knew about weetech.co.uk

All in One Epos System for Takeaways& Restaurants! Reduce Overhead Costs with Weetech’s No Commission Own Branded Online Ordering Websites, MobileApp & Kiosks

Visit weetech.co.uk

Key Findings

We analyzed Weetech.co.uk page load time and found that the first response time was 287 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

weetech.co.uk performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value19.5 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.274

44/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

weetech.co.uk

287 ms

fontawesome.css

290 ms

hover-min.css

374 ms

fullpage.min.css

191 ms

animate.css

377 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 89% of them (24 requests) were addressed to the original Weetech.co.uk, 7% (2 requests) were made to Googletagmanager.com and 4% (1 request) were made to Salesiq.zoho.eu. The less responsive or slowest element that took the longest time to load (754 ms) belongs to the original domain Weetech.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 970.1 kB (79%)

Content Size

1.2 MB

After Optimization

258.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weetech.co.uk main page is 1.2 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. 35% of websites need less resources to load. Javascripts take 741.3 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 6.5 kB

  • Original 9.5 kB
  • After minification 8.6 kB
  • After compression 3.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 6.5 kB or 69% of the original size.

Image Optimization

-3%

Potential reduce by 363 B

  • Original 12.5 kB
  • After minification 12.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. Weetech images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 558.7 kB

  • Original 741.3 kB
  • After minification 741.3 kB
  • After compression 182.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 558.7 kB or 75% of the original size.

CSS Optimization

-87%

Potential reduce by 404.5 kB

  • Original 465.3 kB
  • After minification 439.5 kB
  • After compression 60.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. Weetech.co.uk needs all CSS files to be minified and compressed as it can save up to 404.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (84%)

Requests Now

25

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weetech.co.uk

weetech.co.uk

287 ms

fontawesome.css

fontawesome.css

290 ms

hover-min.css

hover-min.css

374 ms

fullpage.min.css

fullpage.min.css

191 ms

animate.css

animate.css

377 ms

swiperslider.css

swiperslider.css

284 ms

roundslider.min.css

roundslider.min.css

189 ms

bootstrap.min.css

bootstrap.min.css

656 ms

main.css

main.css

378 ms

widget.css

widget.css

379 ms

js

js

57 ms

js

js

101 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

470 ms

bootstrap.min.js

bootstrap.min.js

552 ms

swiperslider.js

swiperslider.js

745 ms

scrollIt.min.js

scrollIt.min.js

465 ms

roundslider.min.js

roundslider.min.js

560 ms

tweenmax.js

tweenmax.js

754 ms

draggble.js

draggble.js

565 ms

ThrowPropsPlugin.js

ThrowPropsPlugin.js

647 ms

morph.js

morph.js

700 ms

widget.js

widget.js

700 ms

typeit.js

typeit.js

743 ms

widget

widget

539 ms

WeeTech.png

WeeTech.png

109 ms

mealzo.gif

mealzo.gif

380 ms

Montserrat-Regular.ttf

Montserrat-Regular.ttf

192 ms

Accessibility Review

weetech.co.uk accessibility score

73

Accessibility Issues

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.

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

Document doesn't have a <title> element

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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 IDs are not unique

SEO Factors

weetech.co.uk SEO score

75

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

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 Weetech.co.uk 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 Weetech.co.uk 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

weetech.co.uk

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