Tools & Wizards About Us
fusionseo.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

fusionseo.com

Baltimore SEO Company, Maryland SEO Services DC & VA | FusionSEO

Page Load Speed

6.3 sec in total

First Response

145 ms

Resources Loaded

5 sec

Page Rendered

1.2 sec

fusionseo.com screenshot

About Website

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

Looking for a professional local SEO company in Baltimore? FusionSEO is the leading Maryland SEO Service provider offers professional services throughout Washington DC and VA. We have earned great rev...

Visit fusionseo.com

Key Findings

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

fusionseo.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value27.0 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value30.2 s

0/100

10%

Network Requests Diagram

www.fusionseo.com

145 ms

material-icons.min.css

163 ms

font-awesome.css

176 ms

mobirise-icons.css

179 ms

style.css

253 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 83% of them (85 requests) were addressed to the original Fusionseo.com, 11% (11 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (821 ms) belongs to the original domain Fusionseo.com.

Page Optimization Overview & Recommendations

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

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fusionseo.com main page is 2.3 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 111.1 kB

  • Original 138.5 kB
  • After minification 132.2 kB
  • After compression 27.5 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 111.1 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 9.4 kB

  • Original 1.6 MB
  • After minification 1.6 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. FusionSEO images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 115.4 kB

  • Original 369.4 kB
  • After minification 368.1 kB
  • After compression 254.0 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 115.4 kB or 31% of the original size.

CSS Optimization

-25%

Potential reduce by 46.9 kB

  • Original 184.0 kB
  • After minification 183.7 kB
  • After compression 137.1 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. Fusionseo.com needs all CSS files to be minified and compressed as it can save up to 46.9 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (83%)

Requests Now

84

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fusionseo.com

www.fusionseo.com

145 ms

material-icons.min.css

material-icons.min.css

163 ms

font-awesome.css

font-awesome.css

176 ms

mobirise-icons.css

mobirise-icons.css

179 ms

style.css

style.css

253 ms

mobirise-icons-bold.css

mobirise-icons-bold.css

178 ms

style.css

style.css

258 ms

style.css

style.css

246 ms

mobirise2.css

mobirise2.css

257 ms

jarallax.css

jarallax.css

262 ms

progress.min.css

progress.min.css

263 ms

styles.css

styles.css

329 ms

allow-webp-image-public.css

allow-webp-image-public.css

341 ms

cleantalk-public.min.css

cleantalk-public.min.css

341 ms

styles.css

styles.css

480 ms

spam-protect-for-contact-form7.css

spam-protect-for-contact-form7.css

578 ms

style.css

style.css

341 ms

main.css

main.css

488 ms

basic.min.css

basic.min.css

425 ms

theme-ie11.min.css

theme-ie11.min.css

419 ms

theme.min.css

theme.min.css

422 ms

elementor-icons.min.css

elementor-icons.min.css

505 ms

custom-frontend.min.css

custom-frontend.min.css

512 ms

swiper.min.css

swiper.min.css

506 ms

e-swiper.min.css

e-swiper.min.css

561 ms

post-7.css

post-7.css

567 ms

global.css

global.css

590 ms

widget-heading.min.css

widget-heading.min.css

586 ms

widget-text-editor.min.css

widget-text-editor.min.css

591 ms

widget-image.min.css

widget-image.min.css

642 ms

post-1324.css

post-1324.css

654 ms

mo_forms_css.min.css

mo_forms_css.min.css

666 ms

intlTelInput.min.css

intlTelInput.min.css

673 ms

css

css

48 ms

jquery.min.js

jquery.min.js

821 ms

jquery-migrate.min.js

jquery-migrate.min.js

671 ms

analytics.js

analytics.js

37 ms

js

js

80 ms

api.js

api.js

78 ms

95.css

95.css

734 ms

allow-webp-image-public.js

allow-webp-image-public.js

577 ms

apbct-public-bundle.min.js

apbct-public-bundle.min.js

660 ms

spam-protect-for-contact-form7.js

spam-protect-for-contact-form7.js

583 ms

jquery.json.min.js

jquery.json.min.js

582 ms

gravityforms.min.js

gravityforms.min.js

594 ms

conditional_logic.min.js

conditional_logic.min.js

566 ms

utils.min.js

utils.min.js

585 ms

intlTelInput.min.js

intlTelInput.min.js

583 ms

hooks.min.js

hooks.min.js

753 ms

i18n.min.js

i18n.min.js

754 ms

index.js

index.js

676 ms

index.js

index.js

675 ms

main.bundle.js

main.bundle.js

677 ms

dom-ready.min.js

dom-ready.min.js

675 ms

a11y.min.js

a11y.min.js

675 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

599 ms

vendor-theme.min.js

vendor-theme.min.js

595 ms

scripts-theme.min.js

scripts-theme.min.js

592 ms

wp-polyfill.min.js

wp-polyfill.min.js

541 ms

index.js

index.js

572 ms

dropdown.min.js

dropdown.min.js

567 ms

webpack.runtime.min.js

webpack.runtime.min.js

581 ms

frontend-modules.min.js

frontend-modules.min.js

597 ms

core.min.js

core.min.js

544 ms

frontend.min.js

frontend.min.js

545 ms

jarallax.js

jarallax.js

492 ms

typed.js

typed.js

484 ms

smooth-scroll.js

smooth-scroll.js

480 ms

index.js

index.js

482 ms

navbar-dropdown.js

navbar-dropdown.js

430 ms

as-pie-progress.min.js

as-pie-progress.min.js

427 ms

vimeo_player.js

vimeo_player.js

418 ms

script.js

script.js

412 ms

8986a971600e8621a33b3a311d517a73.gif

8986a971600e8621a33b3a311d517a73.gif

322 ms

fusion-logo-holder-1.svg

fusion-logo-holder-1.svg

213 ms

baltimore-night-back-3-scaled.jpg

baltimore-night-back-3-scaled.jpg

312 ms

digital.png

digital.png

309 ms

baltimore-md-background-1-scaled.jpg

baltimore-md-background-1-scaled.jpg

298 ms

google-keyboard.jpg

google-keyboard.jpg

299 ms

video-background-dark-blue.jpg

video-background-dark-blue.jpg

311 ms

bright-edge.png

bright-edge.png

315 ms

im-looking-to-1.jpg

im-looking-to-1.jpg

312 ms

rank-3-1.jpg

rank-3-1.jpg

316 ms

why-fusion-scaled.jpg

why-fusion-scaled.jpg

314 ms

collect

collect

69 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

50 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

64 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

146 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

158 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

165 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

162 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

162 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

163 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

159 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

164 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

165 ms

mobirise-icons.ttf

mobirise-icons.ttf

164 ms

icons-mind.woff

icons-mind.woff

167 ms

icon54-v3.ttf

icon54-v3.ttf

168 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

258 ms

js

js

128 ms

socicon.ttf

socicon.ttf

208 ms

mobirise2.ttf

mobirise2.ttf

124 ms

Accessibility Review

fusionseo.com accessibility score

80

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

ARIA progressbar elements do not have accessible names.

High

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

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

Links do not have a discernible name

Best Practices

fusionseo.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fusionseo.com SEO score

100

Search Engine Optimization Advices

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 Fusionseo.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 Fusionseo.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

fusionseo.com

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