Tools & Wizards About Us
mobiecom.tech screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

mobiecom.tech

Mobile-first storefront designed for WebSphere Commerce

Page Load Speed

2.8 sec in total

First Response

48 ms

Resources Loaded

2.2 sec

Page Rendered

546 ms

mobiecom.tech screenshot

About Website

Click here to check amazing Mobiecom content. Otherwise, check out these important facts you probably never knew about mobiecom.tech

Mobiecom is a mobile-first UI storefront designed for HCL IBM WebSphere Commerce and WebSphere Commerce

Visit mobiecom.tech

Key Findings

We analyzed Mobiecom.tech page load time and found that the first response time was 48 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

mobiecom.tech performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value4,030 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.166

71/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

Network Requests Diagram

mobiecom.tech

48 ms

mobiecom.tech

137 ms

js

66 ms

style.min.css

33 ms

styles.css

56 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 64% of them (69 requests) were addressed to the original Mobiecom.tech, 8% (9 requests) were made to Youtube.com and 8% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Mobiecom.tech.

Page Optimization Overview & Recommendations

Page size can be reduced by 381.8 kB (18%)

Content Size

2.2 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobiecom.tech main page is 2.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. 80% 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 65.6 kB

  • Original 83.2 kB
  • After minification 80.3 kB
  • After compression 17.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 65.6 kB or 79% of the original size.

Image Optimization

-17%

Potential reduce by 218.6 kB

  • Original 1.3 MB
  • After minification 1.0 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, Mobiecom needs image optimization as it can save up to 218.6 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

-12%

Potential reduce by 72.7 kB

  • Original 583.6 kB
  • After minification 583.6 kB
  • After compression 510.9 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 72.7 kB or 12% of the original size.

CSS Optimization

-11%

Potential reduce by 24.9 kB

  • Original 232.3 kB
  • After minification 232.3 kB
  • After compression 207.3 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. Mobiecom.tech needs all CSS files to be minified and compressed as it can save up to 24.9 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 69 (75%)

Requests Now

92

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobiecom.tech

mobiecom.tech

48 ms

mobiecom.tech

mobiecom.tech

137 ms

js

js

66 ms

style.min.css

style.min.css

33 ms

styles.css

styles.css

56 ms

orbit.css

orbit.css

86 ms

nectar-slider.css

nectar-slider.css

88 ms

portfolio.css

portfolio.css

120 ms

style.css

style.css

91 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

93 ms

grid-system.css

grid-system.css

95 ms

style.css

style.css

137 ms

element-vc-separator.css

element-vc-separator.css

117 ms

element-vc-icon-element.css

element-vc-icon-element.css

116 ms

caroufredsel.css

caroufredsel.css

124 ms

css

css

40 ms

responsive.css

responsive.css

125 ms

ascend.css

ascend.css

129 ms

menu-dynamic.css

menu-dynamic.css

128 ms

js_composer.min.css

js_composer.min.css

132 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

153 ms

css

css

49 ms

jquery.min.js

jquery.min.js

175 ms

jquery-migrate.min.js

jquery-migrate.min.js

189 ms

frontend-gtag.min.js

frontend-gtag.min.js

152 ms

js

js

83 ms

magnific.css

magnific.css

282 ms

core.css

core.css

284 ms

core.min.js

core.min.js

296 ms

menu.min.js

menu.min.js

295 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

298 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

297 ms

wp-polyfill.min.js

wp-polyfill.min.js

300 ms

dom-ready.min.js

dom-ready.min.js

298 ms

hooks.min.js

hooks.min.js

299 ms

i18n.min.js

i18n.min.js

301 ms

a11y.min.js

a11y.min.js

299 ms

autocomplete.min.js

autocomplete.min.js

299 ms

wpss-search-suggest.js

wpss-search-suggest.js

300 ms

index.js

index.js

393 ms

412742.js

412742.js

79 ms

orbit.js

orbit.js

393 ms

touchswipe.min.js

touchswipe.min.js

393 ms

anime.js

anime.js

366 ms

nectar-slider.js

nectar-slider.js

346 ms

imagesLoaded.min.js

imagesLoaded.min.js

314 ms

isotope.min.js

isotope.min.js

388 ms

salient-portfolio.js

salient-portfolio.js

390 ms

caroufredsel.min.js

caroufredsel.min.js

381 ms

js

js

179 ms

analytics.js

analytics.js

174 ms

salient-social.js

salient-social.js

363 ms

jquery.easing.js

jquery.easing.js

366 ms

jquery.mousewheel.js

jquery.mousewheel.js

359 ms

priority.js

priority.js

370 ms

transit.js

transit.js

368 ms

waypoints.js

waypoints.js

367 ms

hoverintent.js

hoverintent.js

363 ms

magnific.js

magnific.js

360 ms

superfish.js

superfish.js

360 ms

init.js

init.js

423 ms

comment-reply.min.js

comment-reply.min.js

380 ms

js_composer_front.min.js

js_composer_front.min.js

330 ms

js

js

202 ms

nCYTJHlcQ6E

nCYTJHlcQ6E

285 ms

H_bik3xFUp0

H_bik3xFUp0

298 ms

insight.min.js

insight.min.js

324 ms

logo-light-large.png

logo-light-large.png

317 ms

loading.gif

loading.gif

271 ms

header-border.png

header-border.png

270 ms

mobiecom-whitepaper-hero.png

mobiecom-whitepaper-hero.png

488 ms

pin.png

pin.png

350 ms

monitor-phone.png

monitor-phone.png

349 ms

cup.png

cup.png

348 ms

ZobristLogo.png

ZobristLogo.png

348 ms

footer-border.png

footer-border.png

447 ms

collect

collect

110 ms

412742.js

412742.js

328 ms

banner.js

banner.js

328 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

300 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

306 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

368 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

372 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

372 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

368 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

372 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

368 ms

icomoon.woff

icomoon.woff

346 ms

main-image-november-2017.jpg

main-image-november-2017.jpg

1031 ms

www-player.css

www-player.css

40 ms

www-embed-player.js

www-embed-player.js

123 ms

base.js

base.js

375 ms

collect

collect

293 ms

ga-audiences

ga-audiences

536 ms

ad_status.js

ad_status.js

359 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

303 ms

QGccEJWqd_gIzr4UnyRjJu4DFpzUq3q8RcWI0eePlNs.js

QGccEJWqd_gIzr4UnyRjJu4DFpzUq3q8RcWI0eePlNs.js

237 ms

embed.js

embed.js

79 ms

collect

collect

146 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

17 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

15 ms

Create

Create

43 ms

Create

Create

369 ms

id

id

203 ms

qoe

qoe

18 ms

log_event

log_event

1 ms

nCYTJHlcQ6E

nCYTJHlcQ6E

230 ms

id

id

148 ms

Accessibility Review

mobiecom.tech accessibility score

67

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

<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

Heading elements are not in a sequentially-descending order

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

mobiecom.tech best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

mobiecom.tech SEO score

79

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 Mobiecom.tech 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 Mobiecom.tech 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

mobiecom.tech

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