While there has been much public concern about the national healthcare website designed to deliver "Obamacare" to the masses, the Spanish-speaking community has had an extra share of disappointments with trying to enroll for an insurance program.

CuidadoDeSalud.gov, the Spanish-language version of the national healthcare website, is reportedly more difficult and troublesome than its English-language counterpart. The site can send its visitors to state-ran exchanges, but currently, any efforts to actually enroll in a plan are met by a frustrating message that says this feature will be "available soon."

This of course leaves the door wide open for critics of the president's program.

"Hispanics have among the highest uninsured rates in the nation. Yet despite hundreds of millions of dollars devoted to a Spanish-language propaganda campaign, the Spanish-language ObamaCare website hasn't even been launched," Sen. Marco Rubio said in a statement.

Jennifer Ng'andu, health and civil rights policy director at National Council of La Raza, is increasingly vocal in her disappointment with the progress of the site.

"We have been given dates before," Ng'andu told Buzzfeed in a recent interview. "So right now we're not so focused on the dates because I think we understand that this is much more tied to the English-language website.

"For us, if we communicate a date (that) is expected to the community and that doesn't happen, we're going to create more distrust about this system within the community."

For now, visitors to the site are met with the following disclaimer in Spanish: "This is not the application of market coverage. This tool helps you prepare to apply. No information you enter here will move to its application."

Complicating matters, the Spanish-language site was also susceptible to hackers according to Nextgov.com, which said that three different software developers had exposed flaws that would have allowed intruders to steal personal information from visitors as they entered their data into the system. The site administrators reportedly fixed the problem when they were approached by the Web site.