Tools & Wizards About Us
lookr.io screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

lookr.io

Lookr Digital Signage | Kabob Retail Cloud

Page Load Speed

5.9 sec in total

First Response

47 ms

Resources Loaded

4.9 sec

Page Rendered

963 ms

lookr.io screenshot

About Website

Welcome to lookr.io homepage info - get ready to check Lookr best content for Japan right away, or after learning these important things about lookr.io

Lookr supports various contents and touch-screen mode. One can use HTML5 to create multi-display and interactive plug-ins. Simple but powerful.

Visit lookr.io

Key Findings

We analyzed Lookr.io page load time and found that the first response time was 47 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lookr.io performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.2 s

61/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

lookr.io

47 ms

298 ms

css

31 ms

reset.css

291 ms

bootstrap.min.css

312 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lookr.io, 96% (79 requests) were made to Kabob.io and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Kabob.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 518.4 kB (12%)

Content Size

4.2 MB

After Optimization

3.7 MB

  • HTML
  • Images

In fact, the total size of Lookr.io main page is 4.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. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 49.2 kB

  • Original 57.7 kB
  • After minification 43.2 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 14.5 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 49.2 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 469.2 kB

  • Original 4.2 MB
  • After minification 3.7 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, Lookr needs image optimization as it can save up to 469.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 23 (29%)

Requests Now

79

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lookr.io

lookr.io

47 ms

298 ms

css

css

31 ms

reset.css

reset.css

291 ms

bootstrap.min.css

bootstrap.min.css

312 ms

aos.css

aos.css

296 ms

app.css

app.css

302 ms

header_effects.css

header_effects.css

298 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

501 ms

jquery-migrate-3.3.2.min.js

jquery-migrate-3.3.2.min.js

435 ms

parallax.min.js

parallax.min.js

580 ms

waypoints.min.js

waypoints.min.js

582 ms

jquery.mobilemenu.css

jquery.mobilemenu.css

593 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

620 ms

i18n_selector.js

i18n_selector.js

765 ms

header_effects.js

header_effects.js

690 ms

components_import.js

components_import.js

865 ms

lookr_adder_redirect.js

lookr_adder_redirect.js

870 ms

aos.js

aos.js

880 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

1070 ms

main_img_lookr.png

main_img_lookr.png

796 ms

lookr_image_notebook.png

lookr_image_notebook.png

1001 ms

lookr_image_signal.png

lookr_image_signal.png

534 ms

lookr_image_devices.png

lookr_image_devices.png

1158 ms

lookr_screens_img.png

lookr_screens_img.png

593 ms

lookr_feature_1.png

lookr_feature_1.png

1570 ms

lookr_feature_2.png

lookr_feature_2.png

1172 ms

lookr_feature_3.png

lookr_feature_3.png

1412 ms

widget_ticketer_outline.svg

widget_ticketer_outline.svg

952 ms

widget_menu_outline.svg

widget_menu_outline.svg

1097 ms

widget_workflow_outline.svg

widget_workflow_outline.svg

1146 ms

widget_splice_outline.svg

widget_splice_outline.svg

1242 ms

lookr_image_plugin1.png

lookr_image_plugin1.png

1611 ms

lookr_image_plugin2.png

lookr_image_plugin2.png

2059 ms

lookr_image_plugin3.png

lookr_image_plugin3.png

1922 ms

lookr_image_plugin4.png

lookr_image_plugin4.png

2027 ms

lookr_image_plugin5.png

lookr_image_plugin5.png

1862 ms

lookr_image_c1.jpg

lookr_image_c1.jpg

2198 ms

lookr_image_c2.jpg

lookr_image_c2.jpg

2403 ms

lookr_image_c3.jpg

lookr_image_c3.jpg

2052 ms

lookr_image_c4.jpg

lookr_image_c4.jpg

2088 ms

adder_intro.png

adder_intro.png

2177 ms

adder_feature_1.png

adder_feature_1.png

2198 ms

caret-right.svg

caret-right.svg

2206 ms

adder_feature_2.png

adder_feature_2.png

2233 ms

adder_feature_3.png

adder_feature_3.png

2464 ms

adder_feature_4.png

adder_feature_4.png

2374 ms

caret-left.svg

caret-left.svg

2512 ms

adder_feature_5.png

adder_feature_5.png

2353 ms

adder-icon.svg

adder-icon.svg

2456 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

80 ms

adder_ssp_1.png

adder_ssp_1.png

2474 ms

adder_ssp_2.png

adder_ssp_2.png

2469 ms

header.html

header.html

2306 ms

footer.html

footer.html

2366 ms

adder_ssp_ft_1.png

adder_ssp_ft_1.png

2412 ms

adder_ssp_ft_2.png

adder_ssp_ft_2.png

2191 ms

adder_ssp_ft_3.png

adder_ssp_ft_3.png

2293 ms

adder_ssp_ft_4.png

adder_ssp_ft_4.png

2103 ms

adder_join_us_1.png

adder_join_us_1.png

1961 ms

adder_join_us_2.png

adder_join_us_2.png

1846 ms

lookr_bg_1.jpg

lookr_bg_1.jpg

2440 ms

lookr_bg_2.jpg

lookr_bg_2.jpg

2163 ms

kabob_logo.svg

kabob_logo.svg

281 ms

kabob_logo_dark.svg

kabob_logo_dark.svg

478 ms

lookr_logo.svg

lookr_logo.svg

385 ms

voicer_logo.svg

voicer_logo.svg

410 ms

teachor_logo.svg

teachor_logo.svg

425 ms

Union.svg

Union.svg

529 ms

chevroll.svg

chevroll.svg

554 ms

footer_kabob_logo@2x.png

footer_kabob_logo@2x.png

511 ms

mail.svg

mail.svg

559 ms

icon-phone@2x.png

icon-phone@2x.png

611 ms

linkin.svg

linkin.svg

636 ms

instagram.svg

instagram.svg

666 ms

facebook.svg

facebook.svg

700 ms

wechat.svg

wechat.svg

756 ms

QRcode-WeChat.jpeg

QRcode-WeChat.jpeg

927 ms

footer-bg.svg

footer-bg.svg

797 ms

service_icon@2x.png

service_icon@2x.png

800 ms

icon-language@2x.png

icon-language@2x.png

841 ms

icon-dropdown@2x.png

icon-dropdown@2x.png

900 ms

Accessibility Review

lookr.io accessibility score

65

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

lookr.io 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

High

Page has valid source maps

SEO Factors

lookr.io SEO score

82

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lookr.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lookr.io 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

lookr.io

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