Tools & Wizards About Us
mophie.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 0

    Accessibility

  • 0

    Best Practices

  • 84

    SEO

    Google-friendlier than
    53% of websites

mophie.com

Mophie Portable Chargers & Power Banks | ZAGG

Page Load Speed

3.3 sec in total

First Response

156 ms

Resources Loaded

3 sec

Page Rendered

180 ms

mophie.com screenshot

About Website

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

Shop ZAGG's extensive collection of mophie portable chargers, power banks, car chargers, portable batteries, and far more. Browse our mophie selection!

Visit mophie.com

Key Findings

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

Performance Metrics

mophie.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value5,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

mophie.com

156 ms

mophie.com

305 ms

1194 ms

gb

302 ms

gr

294 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Mophie.com, 23% (13 requests) were made to Cdn11.bigcommerce.com and 9% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Zagg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 268.4 kB (36%)

Content Size

750.3 kB

After Optimization

481.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mophie.com main page is 750.3 kB. 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. HTML takes 293.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 253.1 kB

  • Original 293.8 kB
  • After minification 241.4 kB
  • After compression 40.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. This page needs HTML code to be minified as it can gain 52.4 kB, which is 18% 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 253.1 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 144 B

  • Original 244.2 kB
  • After minification 244.0 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. Mophie images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 15.1 kB

  • Original 212.0 kB
  • After minification 211.9 kB
  • After compression 196.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. This website has mostly compressed JavaScripts.

CSS Optimization

-28%

Potential reduce by 80 B

  • Original 281 B
  • After minification 280 B
  • After compression 201 B

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. Mophie.com needs all CSS files to be minified and compressed as it can save up to 80 B or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (74%)

Requests Now

54

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mophie.com

mophie.com

156 ms

mophie.com

mophie.com

305 ms

1194 ms

gb

gb

302 ms

gr

gr

294 ms

gtm.js

gtm.js

173 ms

theme-bundle.polyfills.js

theme-bundle.polyfills.js

84 ms

theme-bundle.main_head.js

theme-bundle.main_head.js

81 ms

main-deeeff52.css

main-deeeff52.css

80 ms

css2

css2

80 ms

theme-98412af0-e958-013c-0814-6e2736edf853.css

theme-98412af0-e958-013c-0814-6e2736edf853.css

144 ms

loader.js

loader.js

138 ms

osano.js

osano.js

70 ms

widget.js

widget.js

314 ms

index.js

index.js

138 ms

117649328.js

117649328.js

69 ms

theme-bundle.907.js

theme-bundle.907.js

117 ms

theme-bundle.79.js

theme-bundle.79.js

116 ms

theme-bundle.720.js

theme-bundle.720.js

118 ms

theme-bundle.datatags.js

theme-bundle.datatags.js

119 ms

theme-bundle.506.js

theme-bundle.506.js

269 ms

theme-bundle.main.js

theme-bundle.main.js

147 ms

csrf-protection-header-95f3d9ac8c049e3ed132c83a168cf1d6a8ed0237.js

csrf-protection-header-95f3d9ac8c049e3ed132c83a168cf1d6a8ed0237.js

118 ms

visitor_stencil.js

visitor_stencil.js

147 ms

exponea.min.js

exponea.min.js

488 ms

js

js

393 ms

js

js

386 ms

hotjar-302169.js

hotjar-302169.js

712 ms

destination

destination

383 ms

bat.js

bat.js

380 ms

quant.js

quant.js

380 ms

ld.js

ld.js

375 ms

image

image

709 ms

mophie-md-web-banner2.jpg

mophie-md-web-banner2.jpg

480 ms

font

font

565 ms

fbevents.js

fbevents.js

492 ms

tag.js

tag.js

610 ms

widget.js

widget.js

604 ms

widget_app_1714479274721.js

widget_app_1714479274721.js

308 ms

index.php

index.php

365 ms

destination

destination

372 ms

nobot

nobot

490 ms

collect

collect

626 ms

activityi;src=10968284;type=counter;cat=zagg-0;ord=315085462690;npa=0;auiddc=887768946.1714925239;u1=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;u2=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;u3=undefined;u4=null;u5=null;u6=null;u7=USD;pscdl=noapi;gtm=45fe4510z89119081182za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F

activityi;src=10968284;type=counter;cat=zagg-0;ord=315085462690;npa=0;auiddc=887768946.1714925239;u1=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;u2=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;u3=undefined;u4=null;u5=null;u6=null;u7=USD;pscdl=noapi;gtm=45fe4510z89119081182za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F

358 ms

rules-p-YMbzZUbMQPN_q.js

rules-p-YMbzZUbMQPN_q.js

292 ms

syncframe

syncframe

302 ms

modules.842bcec28f9fd12bb79e.js

modules.842bcec28f9fd12bb79e.js

248 ms

150 ms

278561706039247

278561706039247

32 ms

pageInfo

pageInfo

152 ms

pixel;r=2077829233;source=gtm;rf=0;a=p-YMbzZUbMQPN_q;url=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;uht=2;fpan=1;fpa=P0-1088881235-1714925239404;pbc=;ns=0;ce=1;qjs=1;qv=b70d35e8-20231208114759;cm=;gdpr=0;ref=;d=zagg.com;dst=0;et=1714925239698;tzo=-180;ogl=;ses=9576f92a-4930-4e5b-976b-b8d2ae33f949;mdl=

pixel;r=2077829233;source=gtm;rf=0;a=p-YMbzZUbMQPN_q;url=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;uht=2;fpan=1;fpa=P0-1088881235-1714925239404;pbc=;ns=0;ce=1;qjs=1;qv=b70d35e8-20231208114759;cm=;gdpr=0;ref=;d=zagg.com;dst=0;et=1714925239698;tzo=-180;ogl=;ses=9576f92a-4930-4e5b-976b-b8d2ae33f949;mdl=

79 ms

wdp.js

wdp.js

68 ms

widget.css

widget.css

81 ms

src=10968284;type=counter;cat=zagg-0;ord=315085462690;npa=0;auiddc=*;u1=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;u2=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;u3=undefined;u4=null;u5=null;u6=null;u7=USD;pscdl=noapi;gtm=45fe4510z89119081182za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F

src=10968284;type=counter;cat=zagg-0;ord=315085462690;npa=0;auiddc=*;u1=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;u2=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F;u3=undefined;u4=null;u5=null;u6=null;u7=USD;pscdl=noapi;gtm=45fe4510z89119081182za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.zagg.com%2Fmophie%2F

111 ms

72 ms

logo.js

logo.js

38 ms

open_sans.css

open_sans.css

30 ms

SEO Factors

mophie.com SEO score

84

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

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mophie.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 Mophie.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

mophie.com

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