Tools & Wizards About Us
photocake.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

photocake.com

PhotoCake® | Personalized Cakes with PhotoCake Edible Images

Page Load Speed

1.5 sec in total

First Response

172 ms

Resources Loaded

1.2 sec

Page Rendered

200 ms

photocake.com screenshot

About Website

Welcome to photocake.com homepage info - get ready to check Photo Cake best content for United States right away, or after learning these important things about photocake.com

Order a personalized cake with PhotoCake® Edible Images. Add your favorite photos to customize your cake! Find bakeries near you with PhotoCake®.

Visit photocake.com

Key Findings

We analyzed Photocake.com page load time and found that the first response time was 172 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

photocake.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

photocake.com

172 ms

stylesheet.css

132 ms

css

62 ms

stylish-select.css

117 ms

jquery.autocomplete.css

99 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 89% of them (68 requests) were addressed to the original Photocake.com, 4% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (477 ms) belongs to the original domain Photocake.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 341.2 kB (41%)

Content Size

828.9 kB

After Optimization

487.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Photocake.com main page is 828.9 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. 30% of websites need less resources to load. Javascripts take 440.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 17.6 kB

  • Original 22.5 kB
  • After minification 20.5 kB
  • After compression 4.9 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 17.6 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 6.5 kB

  • Original 365.8 kB
  • After minification 359.3 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. Photo Cake images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 317.1 kB

  • Original 440.6 kB
  • After minification 409.1 kB
  • After compression 123.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 317.1 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (63%)

Requests Now

73

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

photocake.com

photocake.com

172 ms

stylesheet.css

stylesheet.css

132 ms

css

css

62 ms

stylish-select.css

stylish-select.css

117 ms

jquery.autocomplete.css

jquery.autocomplete.css

99 ms

Rollovers.js

Rollovers.js

133 ms

DropdownTabs.js

DropdownTabs.js

114 ms

swfobject.js

swfobject.js

183 ms

jquery.min.js

jquery.min.js

332 ms

jquery-ui-1.8.15.custom.min.js

jquery-ui-1.8.15.custom.min.js

420 ms

jquery.easing-1.3.js

jquery.easing-1.3.js

222 ms

jquery.stylish-select.min.js

jquery.stylish-select.min.js

239 ms

tinybox.js

tinybox.js

276 ms

scripts.js

scripts.js

316 ms

Images.js

Images.js

295 ms

security.js

security.js

359 ms

ImageLibrary.js

ImageLibrary.js

389 ms

JavascriptHelper.js

JavascriptHelper.js

361 ms

QueryStringHelper.js

QueryStringHelper.js

392 ms

ConsoleHelper.js

ConsoleHelper.js

448 ms

jsxmlsocket.js

jsxmlsocket.js

440 ms

AppConnection.js

AppConnection.js

469 ms

prototype.ashx

prototype.ashx

438 ms

core.ashx

core.ashx

439 ms

converter.ashx

converter.ashx

446 ms

DecoPac.Authentication,DecoPacSite_deploy.ashx

DecoPac.Authentication,DecoPacSite_deploy.ashx

477 ms

DecoPac.AjaxEntry,DecoPacSite_deploy.ashx

DecoPac.AjaxEntry,DecoPacSite_deploy.ashx

459 ms

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

49 ms

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

58 ms

overlay_top.png

overlay_top.png

69 ms

overlaySignin_bottom.png

overlaySignin_bottom.png

70 ms

logo.gif

logo.gif

77 ms

34818.jpg

34818.jpg

67 ms

btn_signin.png

btn_signin.png

76 ms

btn_signout.png

btn_signout.png

73 ms

nav_reports.gif

nav_reports.gif

124 ms

nav_myPhotoCake.gif

nav_myPhotoCake.gif

106 ms

nav_createCake.gif

nav_createCake.gif

115 ms

nav_whyPhotoCake.gif

nav_whyPhotoCake.gif

132 ms

nav_imageLibrary.gif

nav_imageLibrary.gif

168 ms

nav_cakeIdeas.gif

nav_cakeIdeas.gif

169 ms

nav_resourceCenter.gif

nav_resourceCenter.gif

160 ms

nav_contactUs.gif

nav_contactUs.gif

175 ms

dropdownTop.png

dropdownTop.png

187 ms

dropdownBottom.png

dropdownBottom.png

185 ms

top_homeMain.gif

top_homeMain.gif

223 ms

47470.jpg

47470.jpg

391 ms

2.png

2.png

246 ms

3.png

3.png

224 ms

1.png

1.png

241 ms

bg_homeModules2.jpg

bg_homeModules2.jpg

303 ms

bg_homeModules3.jpg

bg_homeModules3.jpg

290 ms

icon_go.png

icon_go.png

283 ms

btn_featured_on.gif

btn_featured_on.gif

309 ms

btn_new.gif

btn_new.gif

337 ms

btn_popular.gif

btn_popular.gif

334 ms

btn_featured.gif

btn_featured.gif

357 ms

btn_new_on.gif

btn_new_on.gif

371 ms

btn_popular_on.gif

btn_popular_on.gif

355 ms

btn_submit.gif

btn_submit.gif

378 ms

arrowLarge.gif

arrowLarge.gif

405 ms

gtm.js

gtm.js

39 ms

bg_nav.gif

bg_nav.gif

385 ms

bg_header.gif

bg_header.gif

442 ms

bg_dropdown.png

bg_dropdown.png

411 ms

bg_homeModules1.jpg

bg_homeModules1.jpg

438 ms

analytics.js

analytics.js

20 ms

DecoPac.Authentication,DecoPacSite_deploy.ashx

DecoPac.Authentication,DecoPacSite_deploy.ashx

394 ms

46800.jpg

46800.jpg

447 ms

scrollbarHome.png

scrollbarHome.png

430 ms

scrollbarHandle.png

scrollbarHandle.png

466 ms

top_footer.jpg

top_footer.jpg

429 ms

ec.js

ec.js

10 ms

collect

collect

10 ms

collect

collect

53 ms

bg_footer.gif

bg_footer.gif

420 ms

Accessibility Review

photocake.com accessibility score

88

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

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.

Best Practices

photocake.com best practices score

75

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

photocake.com SEO score

81

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

High

robots.txt is not valid

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 Photocake.com 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 Photocake.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

photocake.com

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